YAML anchors showing up as config violations?

Feedback & Bug Reports
1

This literally started happening a couple of hours ago. Previously working CircleCI 2.0 configs have stopped working entirely. Example: https://circleci.com/gh/metabase/metabase/26572

My entire company’s CI process, across multiple repos, is now busted due to this change. What gives? Circle, can you fix this ASAP?

2

This was fixed a few hours ago - please retry, and let us know if it’s still a problem.

1 Like
3

@ndintenfass still seeing this – see https://circleci.com/gh/metabase/metabase/26573 for example

4

UPDATE: retrying did not fix this issue, but pushing an empty commit to trigger a new build did.