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.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events