In Bamboo 5.6.1 is it possible to trigger a dependent plan if the parent plan (the plan that triggers) is using the branches features? As far as I understand, you can only trigger a child plan if that child has a branch of the same name. Is that correct? What we want is to trigger the child plan every time any branch in the parent is build without having to duplicate all the branches.
PARENT (branch FOO, branch BAR) -> CHILD
Bamboo works exactly as you described:
As far as I understand, you can only trigger a child plan if that child has a branch of the same name.
We haven't considered scenario you have described:
we want is to trigger the child plan every time any branch in the parent is build
Can you please describe your usecase more? I mean what are the reasons to build a single branch of CHILD whenever any branch of MASTER will be updated?
In our specific case, the MASTER branches are creating an RPM file that needs to be uploaded to S3 and our YUM repository needs to be refreshed. Previously we were doing this as task of each build but now the YUM repository has gotten too large so that this step takes too long. Instead each MASTER branch will create it's RPM artifact and move it to a shared location. Then the idea is to have a dependent CHILD that handles the S3 upload YUM repository updates. This CHILD doesn't really care about branches since it will work on the RPM files in the shared location.
Is this scenario still not being considered?
In my scenario, I'll be having lot of plan branches for release (one or two for each sprint) and hotfix and since the plans and deployment projects have one to one relation, it's a manual process and a pain to do deployment process.
For Continuous Deployments from branches, it would be really helpful if we can have automatic trigger update with active branches in deployment or if we can have the described scenario.
I do have a related scenario. So we're working with JGitflow on 2 projects. ProjectA has a branch Super Cool Feature. Project B also has a feature branch that depends on this project by declaring a maven dependency on project-a-super_cool_feature-1.0.0-SNAPSHOT .
So if a developer pushes changes to Project A's feature branch, I expect that the feature branch of ProjectB is built as well.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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