Undefined Properties in Bitbucket Pipeline

T. Klingenberg

Do Bitbucket sees any problem if the Pipelines validator complains about undefined properrties (at the first level of the file)?

 

We'd like to do YAML references/aliases in the file and add a new property for it inside it (while we could also just reference existing properties which are fine as I just realize while writing the question) and would like to get a carte-blanche from you guys for such a procedure.

 

Example:

image: name:tag

clone:
 depth: 12

undefineproperty:
 - linting: &linting
[...]

 

Can you give carte blanche for that "undefinedproperty"? Any thoughts?

 

Also I'd like to know if it's possible to add properties of our own to the options section.

Philip Hodder

Hi Tom,

While that is valid YAML, the Pipelines validator is set up to verify YAML that strictly follows the definitions we provide in our documentation here: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html

However, our backend parser supports generic YAML so you're references should behave roughly if properly configured.

I'm not sure I understand what you're trying to do here, but this feature request may be somewhat related to what you're asking for: https://bitbucket.org/site/master/issues/12751/allow-more-capable-steps-that-can-be

Thanks,

Phil