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

Bamboo specs yaml: Create different plans

Hey there, 

i think that the current documentation on yaml specs lacks a lot of information. 
So currently i see that i can create one yaml file in my repo which works fine and creates a plan and runs that whenever changes in the repo happen. 

No my questions are: 

how can i define triggers in the yaml spec ?
how can i define several plans for one repo ? 

i currently have a check for code lint issues during a merge request which works fine. 
but now i want to run e.g. integrationchecks after the code has been merged. What is the proper way or is it not possible to define several plans and triggers in a yaml spec ? 

1 answer

1 vote

Hi Dominic,

I'm afraid it is still not possible to define triggers using YAML specs, all currently available library are listed in the Specs YAML documentation

You can define several plans using the same repo only if you put the YAML file in different branches and set these other branches to scan for YAML specs code.

For your use case, I'm pretty sure it will be more appropriate to use Bamboo Java Specs

Thank you.

Gabriel Ribeiro


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events