Today we look at the 2 webhook triggers created and updated for the pull request. There doesn't seem to be enough distinction on "what" was changed/updated in the pull request. It would be nice to have if a the latest commit changes (new or reverted) that we could only trigger our automation when that happens. Currently having our CI/CD server run when the description or title is updated wastes our CI queue time.
Hi @bshuman ,
As well as the changes you described it will also trigger when reviewers are changed or any other PR option like delete branch.
You might want to checkout Flowie, the Bitbucket app we provide, which gives you greater control over when to trigger your CI/CD. By default Flowie's CI/CD integration will trigger only when there are code changes and it also smart to not trigger a build when there is conflict in the PR.
Please feel free to contact our support if you have questions!
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.