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

Linking multiple repositories to a YAML spec repository

We have a single YAML specs repository that has various tools and scripts in it for conducting our tests, but not the code we're testing. We keep our code in many other repositories, and we're hoping to use the specs repository as the one stop shop for those repositories to test with.

I can't find a way to link multiple repositories to this in YAML or in the configuration, only the repository that actually has the specs. Is it possible?

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 02, 2019

Hi @Joseph Clements

YAML specs was designed for less complex builds and therefore lacks in features if compared with JAVA Specs. Recently we had a lot of improvements in YAML specs due to a number of feature requests we received.

At the moment you cannot have other repositories configured/linked to YAML specs. Of course, you can use a script task to checkout your code, but that will not be the same scenario you have when Bamboo does that for you.

There is a JAC ticket requesting this feature to be part of YAML specs:

To solve this problem now, I would recommend you migrating your YAML configuration to JAVA specs.

In case you are not familiar with JAVA specs, the main configuration is already available for you through  Actions >> View plan as Java Specs :

Screen Shot 2019-08-02 at 10.02.56.png

Source or truth on JAVA Specs: Bamboo Java Specs - Atlassian Documentation.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events