Difference between Stopping and Disabling a Fisheye Repository

[Guy Anela]

Sorry, newbie question for ya. What's the difference between Stopping and Disabling a Fisheye Repository. We have a list of Repositrories that aren't currently being used and we're wanting to prevent them from reindexing. We were going to simply disable polling on them but it appears they can manually be reindexed in that state so we're looking to either stop them or stop & disable them. Is stopping it enough or should we also disable the repository? Are there any advantages/disadvantages to one or the other? From first glance, it looks like Disable is is just an added layer that prevents the repository from being started again. Does it do more behind the scenes?

Thanks in advance!

[Renjith Pillai · Accepted solution]

Stop stops a running scan. You won't see the stop option for a repo which is not running, AFAIK.

So you will either do stop and disable or just disable of your repos. Btw, why don't you just delete them if you do not have those data anymore?

[Guy Anela]

Thanks Renjith! Unfortunately we've been bitten before by prematurely deleting a repository that we were told was no longer being used ...so we're simply going to disable them for now. ;)

[Conor]

A stopped repo will start again when FishEye is restarted, whereas a disabled repository will not.

[Guy Anela]

Thanks Conor! Makes sense... I just wanted to make sure there wasn't more to it.