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

Fixing Bamboo yaml spec usage to default branch

Is it possible to force Bamboo to use the Bamboo Specs from default branch (for every branch) instead of using the Bamboo Specs from the specific branch?

If not, what are the options to merge the default branch Bamboo Specs into the specific branches?

I guess that "Automatic branch merging" in the Bamboo Specs is not an option? It seems like the plan is first "set up" and then the merging is applied, so the changes in default branch cannot/will not be considered...



1 answer

0 votes
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 02, 2022 • edited

I think this is possible with Bamboo 8.0.0 and newer. It is also possible with any version of Java Specs.

The way you do it is to store your specs in a different repository than your project code. You'll have then to explicitly defined repository list in your YAML specs to skip the specs repository but check out the project code instead:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events