The Challenge: How to ensure build-time changes to source are preserved without trigger another build?
Current Implementation: Part of our build process updates various src documents with elements like the version-number (only available at build time). It pushes these changes back to the central repository branch (to ensure the information is not lost in future builds) ... but this triggers another build.
We're using Git, and Bamboo v5.4.2 build 4208
All ideas, all alternative approaches, to solving the problem welcome.
It is possible to configure build triggering in Bamboo to ignore changes to specific files. If you can isolate the files that are changed by build process from files that are changed as part of development process that could work for you.
The options is under repository configuration, in 'Advanced' section.
Following on ... I'm finding that the Java Regex (regular expression) I'm using to exclude files doesn't seem to be effective in Plan Branches. The regex is simply:
To match any *.txt file changes.
The Advanced "exclude all changes that match" option is selected, but still it builds on changes to *.txt files.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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