I have a CI task that is incrementing a build number in my git project, and as such, it has to make a new commit to push out the updated build number. This in turn goes into stash which signals bamboo to start a build. Is there a way to suppress this behavior? Either on Stash's end or Bamboos? I guess I could check the commit in bamboo and abort the build if the committer is bamboo - but i'm looking for something more elegant.
Bamboo has provision to automatically trigger build plans if code changes are committed to working rep.
Are you looking for something like run your build plan manually, then probably this doc can help a lot.
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