Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Repository Commit task triggers build, explicit exclusion still triggers spec update

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:Bamboo - Linked Repo - Failing exclusion.png

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)

Bamboo-changes detected.png

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.

AUTO:.*
^AUTO:.*
^AUTO:.*$

 

Finally I tried settings an "Exclude files" pattern. Same as above - the spec configuration is updated but a build does't trigger.

Bamboo - Linked Repo - Working exclusion.png

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.

 

Regards,

Franky

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

248 views 4 6
Read article

Community Events

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

Events near you