Optimal route to file-triggered build

We've finished our Bamboo evaluation and are beginning the (slow) process of migrating a 10-year in-production project into the care of Bamboo.

Our version numbering is currently manual, someone edits proj/VersionNo.h and checks it in. We use <product version>.<release number>.<patch number>.<build no> where build no is actually a 0-255 value within the first three quads, e.g. 1.34.0.0 is the first build of product version 1, release 34, patch 0.

I have a nightly all-configurations build that I want to trigger automatically any time proj/VersionNo.h is checked in, and then when that is working, I want to add a plan to run a script that updates VersionNo.h...

It seems like I need to create a new plan which monitors proj/VersionNo.h for checkins, which is a parent project for the daily build.

And then create a parent project to that which runs the upversion script and checks in the result, and allows it to trigger.

But somehow this doesn't feel right or optimal to me. Would it be better to have the repository telling Bamboo when the file changes and triggering the specific plan?

3 answers

Note: I *think* I can make a single-file based filter by specifying the individual file-path as the subversion repository elsewhere, but (a) I have to start repeating branch names in input fields, (b) I can't have both a scheduled and a repository-scan trigger...

Hello Oliver,

To set up a "Nightly all-configurations build" I'd create a Bamboo Plan that would use *scheduled* *poll* strategy (once per day, at 3am for example). In the plan advanced repository options I'd set the file pattern filter to only trigger the build when it detect a file .*proj/VersionNo.h.* was changed (or similar regexp, you got the idea).

What other plans do you need to set up?

regards,

your repository trigger, if you use one, can look for this partiular file, and trigger the appropriate build. I use a similar strategy to avoid building when only project files (intellij,eclipse) files are checked in.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

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...

1,093 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot