Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Branch plan only updates spec configuration instead of running the actual plan


I had a working plan to create a branch plan whenever a pull-request was opened on Bitbucket. Bamboo would create a branch plan for the pull-request and run the plan.
The plan is created using Bamboo java-specs.

After a commit to change another plan, Bamboo still creates a new branch plan whenever a pull-request is opened, but instead of running the plan, Bamboo just runs an update for the plan configuration "Specs configuration updated".

I have tried to delete and recreate the plans by scanning the bamboo specs again, but the same behaviour persists. I have also made additional changes for the plan that defines the branch plan configuration as well as other bamboo plans, but when a pull-request plan is created it still runs a specs configuration update instead of the specified build jobs and the shows the same commit as the source of the bamboo specs changes.

It seems to me that the plan that defines the branching configuration is somehow out of sync with the bamboo specs even after deleting and recreating all the plans.

Has anyone faced anything similar?


1 answer

Managed to work around the problem by re-creating the pull-request plans by hand using the Bamboo UI and deleting the misbehaving plans and related java-specs.

I will try re-creating the plans from java-specs with different plan keys later. Hopefully that will resolve the issue.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events