Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,644,339
Community Members
 
Community Events
196
Community Groups

How to prevent a bamboo build triggering?

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.

3 answers

1 accepted

1 vote
Answer accepted
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 05, 2014

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.

Thank you Marcin, that was just the thing! Added a regular expression to the excluded trigger-files, which fixes the issue perfectly.

0 votes
Ron Chan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 09, 2014
Try .*/.txt

Thank you Ron. It looks like there is something else responsible, as it works (to stop the build) in some Plan Branches, but not others. I will try to establish what other possible triggers are at work.

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:

.*/*.txt

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.

Any ideas?

Flipskin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 05, 2016

Hello @Andrew Forkes, have you found the answer on your last question? I'm trying to overcome the same issue now

Try   ^.*\.txt$

It's already working for me 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events