In the official documentation I can read:
Ensure that no hooks are configured that will trigger builds if you are using CI tools. If you are using bamboo this will be taken care of when you disable application links. If you use something like Jenkins, you will need to manually disable or delete these hooks.
But I can't find a way to make this job quickly and for all of them.
In my instance, there are many of them and disabling them by hand is really unfeasible.
I can't even imagine asking every team to disable theirs by hand...
Can you suggest a way to disable all webhooks, post webhooks and hooks from any project/repo with a batch operation?
I'm cloning the production instance and I want to be sure that people making a test on a staging instance does not trigger something to the production systems (as correctly stated on Atlassian docs)
By looking at the SQL database it seems to me that there are a lot of them. We have hundreds of projects with thousands of repos.
I looked in the AO_A0B856_WEBHOOK table and sta_repo_hook but I don't know if they are all, if it is ok to disable them from the database when Bitbucket is powered off, etc...
Can you give some hints?
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events