I have master with branching enabled, it's working well.
I have created a ReleaseCandidate branch but need only the build stage to be run, not all of the tests, as the QA team are to run their whole suite over it and the CI test suite is time consuming.
(I also want to change notifications, add a few envVars, change the branch cleanup options, etc)
Can I specify that I want /this/ branch to run /that/ config without impacting the parent (Master) ?
if not, how do I achieve this ?
The way I've resolved this is, indeed, cloning a plan and tailor it to your needs. Unfortunately you will have to sync updates manually yourself.
There is also a plugin wihich lets you dynamically update the workflow but not notifications, cleanup etc. https://marketplace.atlassian.com/plugins/org.valens.dynamicPlans/server/overview
Have followed your advice, have cloned the build plan and setup a new proj, with one build plan, have changed the notifications, the build stages and variables etc. it's now looking like I'd like it to, only ... I can't get it to auto update from Master which is being built in the original plan.
This is a nightmare! I don't understand why we can't 'tear off' a build plan for a branch and hone it to that branch's specific reqs.
Maybe this plugin is something you would like:
Set the master plan as template and let your branch plan use the templated jobs steps
Thanks Mark, appreciate your guidance.
Sadly, this is looking like a real heartache.
Master has branching enabled and it's working a dream for all branches. However, we have a special, critical branch, for which we don't want to run the whole plan, just a subset of it and we want to manipulate some bits so that only our demigod receives notifications etc.
I don't want to change the WORLD for this one branch. It seems like such a simple thing. I can't believe it's not possible.
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