nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do you configure bamboo specs for plan branches

Chris Johnston_zbi0y1

I have a java bamboo spec configured on the configured master repository. This works fine whenever I make a commit to master. If the plan changes, it updates the plan and then you can run it, etc.

However, the plan uses feature branches, and is configured to create a plan branch any time a new feature-branch is created.

What I'd like to have happen, is for bamboo to also update the build plans for these feature branches. The feature branch itself may have changes to how the builds are done.

I cannot figure out how to configure bamboo to also look for changes to the bamboo-specs build plans on the feature branches.

Any help is appreciated.

Accepted answers

All comments

Robert W_noca3r

Chris,

If you have Repository Stored Bamboo Specs, any time a commit is pushed to the Specs Repository, Bamboo will reconfigure the defined build plans according to the new Specs.

If you'd like to manage Plan Branches with Bamboo Specs, please refer to the Plan Branches section of the below article:

Bamboo Specs Documentation

Vaisakh PS

@Robert W - Good One. But how can i override the variables after creating the plan branch using Java Specs. In the above docs it's given to automatically create branches using specs, but no code samples how to update the branch specs variables. It will be much appreciated if you can give some code samples of the above req.

Chris Johnston_zbi0y1

This doesn't answer the question.

I have a repository, [repository], on the master branch of that repository I have the following two areas:

bamboo-specs\

PlanMasterPlan.java

src\

Within the configuration of Bamboo, I have spec polling enabled. The default 'branch' of [repository] is set to master.

Within PlanMasterPlan.java amongst the other jobs/tasks it does, it sets up the plan to support plan branches,

      /* Setup plan branches */
      plan.planBranchManagement(new PlanBranchManagement()
              .createForVcsBranchMatching("feature/.*|bugfix/.*")
              .delete(new BranchCleanup()
                      .whenRemovedFromRepositoryAfterDays(7)
                      .whenInactiveInRepositoryAfterDays(30))
              .notificationLikeParentPlan());

Now, lets assume that is all deployed. This means, that when my developer goes into bitbucket (or however) and creates a new branch called feature/JIRA-1234...

Then a new branch will be created in bitbucket for them to work, and additionally, bamboo will create a new plan branch for JIRA-1234 and compile it to achieve build #1 as per the current config spec.

Next, the developer uses git and switches to feature/JIRA-1234 branch and begins coding.

At some point, they decide the build plan needs updating, so they navigate to the bamboo-specs\ directory within branch feature/JIRA-1234 and makes changes.

They then commit those changes and push them to bitbucket.

At this point is where the problem occurs. This push does not trigger bamboo to refresh the build plan. Instead (assuming a trigger is enabled in the plan), it attempts to execute the plan as it is defined in the master branch (what is currently deployed in bamboo). Of course, since the developer just made a change to it in his branch (presumably to support some new code he wrote in the same branch), this build will now fail.

The only way I can see to resolve this would be to either publish the new plan manually (in which case you might as well disable the spec polling in the repo) or push the bamboo-spec code directly to master instead of your branch.

There are lots of problems with either of these approaches.

Bruce Szalwinski_f6dror

See https://jira.atlassian.com/browse/BAM-19620

vpogrebi

This is NOT an answer, but rather yet another "complaint" related to Bamboo Branch Plan implementation...

What my team has learned (the "hard way") - is that when main build plan (usually associated with the 'master' branch) gets rebuilt (in our particular case - we are converting existing plans to be based on repository-stored Java specs), branch plans do not get automatically rebuilt at the same time. In a sense, branch plans kind-of "divert" - which is demonstrated in some global Bamboo variables (example: ${bamboo.planRepository_repositoryUrl} and ${bamboo.planRepository_branch}) be not set during branch plan execution at all, and instead - "numbered" variables (${bamboo.planRepository_1_repositoryUrl} and ${bamboo.planRepository_1_branch}, ${bamboo.planRepository_2_repositoryUrl} and ${bamboo.planRepository_2_branch}) are being set.

We had some script tasks that used these global variables (${bamboo.planRepository_repositoryUrl} and ${bamboo.planRepository_branch}) - which got "broken" because of this. It took use very long time (testing/debugging) to figure out what caused these issues. Now we know that whenever main plan is rebuilt - it is necessary to (manually) rebuild (delete and recreate) branch plans...

Roy van de Korput

Found a solution for this @Chris Johnston ? I see the same issue...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

spec