Actually you can find the schema here, as part of the vscode extension:
However, it has a lot of problems, so I wouldn't rely on it.
If I have time I could submit a pull request for my issues, but I'm sure Atlassian could do a better job since they already have a pipelines validator.
I would be nice if it supported steps definitions, like it was requested in that ticket too. We use them quite frequently, since we reuse steps in various pipelines.
I have a fix for that, but it was a quick solution that didn't consider other use cases, so I wouldn't feel comfortable making it public :)
Well, any piece of YAML can be reused, it's not limited just to steps. What I mean is that an anchor can be declared anywhere in the schema, and used later on. definitions object is just a conventional place to keep reusable pieces.
I don't think adding steps to definitions is a good idea. It'd only help with configs for some users, potentially small number of them. Others would want to reuse parallel, or maybe variables – should we add them do definitions too? Of course, we can add every single entity type as a possible child of definitions, but that would really clutter the schema.
Finally, validation should actually kick in where you use the anchor. That is, it will work as if the anchored bit is inlined. It then depends on how good the validator is in terms of whether the error it shows makes any sense (for instance, IntelliJ is not great here, I'm not sure about VS Code).
Especially since your own parser appears to reject yaml which adheres to the structure specified in your documentation. It would be really nice if 'condition' worked as advertised, since there is no schema I can look at to see how it is supposed to be. The docs cover it, but using it as specified results in an error
Hello @Sam Gendler,
Can you provide an example which didn't work for you?
There is a more recent JSON schema than linked above – can you please check if your example is validated against it? However be aware that it is not an official schema for Pipelines configuration YAML either, and it is maintained on the best effort basis.
Let me know if this helps.
We dont currently publish a schema for our yaml format :(
The closest we have is you could create one based on the description of our yaml as described here: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events