I can see there's a way to configure variables against specific branch plans, once they have been created, but is there a way to set some defaults that only apply to branch plans that are automatically created (when the code branch is pushed into Stash?)
One case is where I need SonarQube to run in incremental/preview analysis in all branches, and only run in full "analysis" mode when the main plan builds.
Bamboo doesn't have that feature (yet), but I think you can still achieve what you need. Here's how:
The name of the current branch is available in variable called bamboo.planRepository.branchName. You can match this against 'master' (or whatever your main branch is called).
Now, if you run SonarQube from script task then the rest is easy. Things get a bit complicated if you absolutely need some Bamboo variables to be set. In that case:
In case you have multiple Jobs in your build, you might want to create a 'preparation stage' that would produce all the variables. If you set 'result' scope in the Inject Variables Task, the variables become available in all subsequent stages of the plan. (and not just the current Job)
Note that the above applies to Bamboo 5.7 and later.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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...
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!
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