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!
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot