I have a pipeline which performs a build, increments the package version and commits and pushes the result back into the branch. Currently this causes an infinite build cycle.
In other systems, it is possible to prevent this by including a special tag in the commit message; for example including [ci skip] in the commit message.
Can this be done?
One way would be to switch branch in the script and check the updated code into a branch which does not trigger a pipeline. I was wondering if there is an alternative?
we had a similar issue with some of our projects that use maven. To solve the issue we created a separate 'release' branch. Our workflow looks like this:
Let me know if this helped you?
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