Shared Config and Anchors

[hhslepicka]

Is it possible to create and use anchors via the new shared configs mechanism?

[Montana]

Hey @hhslepicka,

Welcome! Have you looked at this?

Travis CI Documentation

[hhslepicka]

Hey @Montana,
Thank you!

Yes, I looked into that.
What I would like to do is to leverage the new shared config at Travis with the import mechanisms and import existing anchors at my .travis.yml file or even other shared configs but unfortunately that does not seem possible at least at my tests.

The files are imported but the anchor is never properly replaced as I believe it is evaluated when the file is loaded and before joining the templates.
Is that correct?

Is there a way around it?

[hhslepicka]

@Montana do you happen to have a way around the usage of anchors coming from files imported via the new shared config mechanism?

What I would like to do is to define standard procedures at yaml files that later can be reused and imported to compose a .travis.yml with those common anchors.

[roman.hosek]

Unfortunately, it’s not supported:

Imported anchors not working

This is not supported. Anchors and aliases are an internal detail in YAML 1.1 – when a YAML is parsed, all aliases are expanded using corresponding anchors and neither are present in the parse result. Travis combines parse trees rather than raw text (since it needs to parse the file to find out whether it needs to import anything) so it cannot do anything about anchors at that point.