This documentation relates to an earlier version of FishEye.
View

Unknown macro: {spacejump}

or visit the current documentation home.

You can carry out operations such as stopping a repository scan, restarting a repository scan, disabling it, etc, via the repositories list or repository summary screens.

To access the operations for a repository,

  1. Click the menu labelled with your user name in the the FishEye/Crucible header, and click the 'Administration' option. You will need to be logged in as an administrator to see this link. The FishEye/Crucible administration console will be displayed.
  2. Click the 'Repositories' link. The list of repositories set up in your FishEye instance will be displayed.
  3. Click the name of the repository, (under the 'Name' column in the list of repositories). The Repository Options for the repository will be displayed in a dialogue.
  4. A number of repository operations will be available next to the 'Actions' field:
    • 'Stop' ('Running' repositories only) — Stop the repository.
    • 'Restart' ('Running' repositories only) — Restart the repository.
    • 'Enable' ('Disabled' repositories only) — Enable the repository.
      (info) More repository actions are available via the Repositories list. See Managing Your Repositories.
  • No labels

3 Comments

  1. David Rosenfeld

    Jul 15, 2010

    Does a "Stop" followed by a "Restart" equate to a pause/resume operation, or will it restart the repository scan from the beginning?  Our initial repository scan (following a combination of a version upgrade and migration to new server hardware) has been consistently spiking to 99%+ CPU utilization with occasional dips, and we are getting feedback from our users that the tool is currently unusable due to exceedingly slow response time.  If we can pause the scan for a short time to allow some code-review activities to proceed, and then restart the scan, that would help us satisfy the needs of our user base.

    1. Gavin Baumanis

      Sept 27, 2011

      I realise the initial comment is old but for those that come here afterwards...

      Great Question : I had the same problem here; So I tried it out.

      If you stop the repository  / then restart it - it simply resumes where at the point it was at in the scan, prior to being stopped.

      1. Anonymous

        Apr 20, 2012

        This is probably the case once the initial load is done, but during initial load, I experience that sopping a repository seems to loose a lot of work done (example When I stop the repo it was indexing revision 151000, I shutdown crucible, when I restart it it "rolled back" to 137 000 !). So be careful during inital load if you do not want to reindex multiple times the same data.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.