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

This widget could not be displayed.

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

This widget could not be displayed.

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,

This widget could not be displayed.

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 Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

99 views 1 0
Join discussion

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