You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Before start I'm using Bamboo YALM Specs
I'm testing the new version of Bamboo and it was great to add Divergent branches, but I'm testing that and is only possible divergent branch for Plans.
I want to update in my Dev branch the Plan and the Deployment step and it's not possible.
I can see the changes for Plan but for deployment, it's not possible as a workaround I tried to add another deployment structure with a different name but still don't showing in Deploy part.
This someone know what is the best way to do that?
Thanks a lot for getting in touch with Atlassian's Community and posting your question here in the Bamboo section.
Well, first thing to say, divergent branches are officially called Specs branches and that's so because you must be using Bamboo Specs so to utilize them. Bamboo 7.0.x supports this new feature for Java and also for YAML Specs.
Please find our Bamboo Specs Tutorial as a great reference for you.
Basically Specs branches are enhancing the Bamboo plan branch feature. They now break especially with one former limitation, namely plan branch configuration being inherited from the master build configuration.
So Specs branches are now capable of creating custom build plans working on any feature branch differnt from master. And that makes them far mor flexible e.g. by using their own triggers, stages or even jobs.
However, there are some further prerequisits to take into account other than that they can only be used per "configuring as code".
Though, this feature also comes along with some limitations, like default repository is inherited from the master and cannot be changed and also the below one
Plan branch configuration is not available for deployment projects. Bamboo ignores any Bamboo Specs on deployment projects in plan branches.
which is stated in Enhanced plan branch configuration and that is exactly what you aimed to do.
However, typically this is not a requirement since a deployment is supposed to be connected to a build plan.
Thus you should be able to use Specs branches for builds, and there have all flexibility needed. So what is built or fetched from the repository in your build plan, you may use as is or package it and either share it as an artifact with a deployment environment or also copy it out per a Bamboo SCP task, for example.
We hope that this clarifies things and still allows you to use Specs branches.
In case you'd have any further doubt or concern or see an urgent need to use Specs branches from within a deployment environment, please come back to as per this thread.
Thanks and all the best,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.