Purpose

This article describes a way to prevent Fisheye and Crucible from scanning new revisions for your Subversion repository while making sure it stays accessible to your users.

• Stopping the Subversion repository inside Fisheye and Crucible is not really an option because the repository becomes inaccessible once it's stopped.
• Replacing the credentials used to authenticate against the Subversion repository to force the connection to fail works but the repository starts reporting several errors. The application logs will get clogged with errors related to the authentication failure.

Solution

There's no "read-only" option inside Fisheye and Crucible that will easily allow to put the scanning process on hold but there are alternatives. The best way to achieve a "read-only" stateus for your Subversion repository is to:

1. Access the Fisheye and Crucible Administration > Repository Settings > Repositories page.
2. Find your Subversion repository in the list of repositories and click on Actions > View...
3. Go to the Updates tab.
4. Make the "Use the system default settings for updates" option is unchecked.
5. Check the "Disable polling" option.

From this moment on Fisheye and Crucible will no longer automatically scan the repository for changes. It's important to note that the scan process will still occur in case:

• Someone accesses the repository configuration inside the Fisheye and Crucible administrative area and click the "Run Incremental Index" for that repository.
• An SCM commit hook was previously set up inside the Subversion repository and commits are triggering the scan process via the REST API.

You have to make sure no one but the Fisheye and Crucible administrator has permissions to manage the repository and no SCM commit hook has been set up inside the Subversion repository to make this work.