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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,703
Community Members
 
Community Events
176
Community Groups

How do I link my plan to a repo that is not part of the YAML Specs repo?

According to the best practice where Specs are live in a separated repo from the application's repo.  But how would one link the plan's repo for YAML Specs implementation?  Nothing is mentioned in the doc.

https://docs.atlassian.com/bamboo-specs-docs/6.9.2/specs.html?java#creating-linked-repositories

1 answer

1 accepted

1 vote
Answer accepted

Hi @Vinh Hong

You need to add bamboo-specs/bamboo.yaml in the root of the source repository used to checkout your code in Bamboo. YAML specs is only able to process one repository and this repository needs to be the same where the bamboo.yaml file is located.

YAML Localization

Every YAML Specs file should be inside the bamboo-specs folder, on the root of your repository.

The bamboo.yaml is the root file for all your definitions.

I consider that this information is not very easy to find today and that is why I opened a feature request to improve its location:

 

I hope that helps.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events