nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bamboo YAML specs dont work YAML Anchors

unknown

I'm creating a bamboo.yml with 2 plan and I want to reuse this code as YALM anchors.
But at the moment when I use that in YALM file I get the error below:

Bamboo YAML import failed: Invalid format of the YAML file: found undefined alias stages
 in 'reader', line 79, column 7:
      <<: *stages

Can I use YAML Anchors in my bamboo specs?

Accepted answers

Victor Debone_qkmjhv

Hello @[deleted] welcome to the community

Yes, you can use YAML Anchors in your Bamboo Specs, but with some precautions.

If I see correctly, you tried to declare stages on one document (plan) and tried to re-use the same stages on a second document (plan). Bamboo YAML Specs does not support cross-document anchors and in your case it won't work.

Alternatively, you can make the use of Includes as a workaround this limitation. You would create a separated YAML file with the definition of your stages, and then include them as the stage of both your plans.

Is that a good fit for you?

All comments

Victor Debone_qkmjhv

Hello @[deleted] welcome to the community

Yes, you can use YAML Anchors in your Bamboo Specs, but with some precautions.

Is that a good fit for you?

unknown

Yes, that IS a good idea.

Other question is.

I want create 2 plan in the same yalm file one for branch develop and other for Branch master.

But the problem is I put the bamboo.yml in the branch Branch master and created a linked repository for this repo and branch, but when I run the plan only clone the master and I can't clone the develop Branch.

Have any way to resolve this problem?

At the moment I create one bamboo.yml in master branch with the prod definitions and other in Develop branch with dev definitions, but if any dev make a mistake and merge the bamboo.yml from dev to master I'll have a problem

Victor Debone_qkmjhv

Great that it might work for you!

For the second question you will need to wait a bit more. This is a highly-requested feature that Bamboo currently doesn't support. The workaround is to maintain a plan for master and a second one for development, but in different linked repositories.