You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As part of my deploy I am updating a .version file in the repository and committing via a Repository Commit task.
The message of this commit is "AUTO: Updated release version"
According to the doco Bamboo should automatically ignore commits made via a Repository Commit task, but instead I got an infinite loop that I had to manually kill. (Due to an unrelated issue it kept appending to the release version "1.0.0_(2)_(2)_(2)_(2)_(2)_(2)_(2)...")
Next I tried setting an "Exclude changesets" pattern on the Linked Repository:
This was a partial success in that it didn't trigger a build, but it did trigger a plan change (my .version file is in the bamboo-specs folder)
I presume this partial success indicates that the regex is working, but the behavious is not as I'd expect. I tried a few variations just in case, same result for each.
Finally I tried settings an "Exclude files" pattern. Same as above - the spec configuration is updated but a build does't trigger.
I'm on Bamboo 7.1.1 (70117), using Java Specs from source control (via the Linked Repo)
Can anyone tell me if
a) The behaviour of the Repository Commit task is correct or a bug
b) The behaviour of the change detection exclusion is expected
I'm getting used to things not working quite right with bamboo specs, so it would be great to get another opinion on whether my expectations are wrong or if something really is behaving oddly.