You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if we could define all our pipelines in a single .woodpecker.yaml file, instead of resorting to holding multiple pipelines in individual files in a dedicated folder. YAML syntax allows for multiple documents to be contained in a single stream by separating them with '---' (triple hyphens). Woodpecker currently doesn't utilized this feature when loading pipelines, since it's the file URI that is passed to - for example - 'genItemForWorkflow' that produces a single item from a single file, even if that file contains multiple documents.
Suggested solution
Allow for including multiple YAML documents within a single file.
This would require a change in some interfaces that currently take a file URI and pass it down to be processed by specialized functions first and extracting a list of YAML documents.
Clear and concise description of the problem
It would be nice if we could define all our pipelines in a single .woodpecker.yaml file, instead of resorting to holding multiple pipelines in individual files in a dedicated folder. YAML syntax allows for multiple documents to be contained in a single stream by separating them with '---' (triple hyphens). Woodpecker currently doesn't utilized this feature when loading pipelines, since it's the file URI that is passed to - for example - 'genItemForWorkflow' that produces a single item from a single file, even if that file contains multiple documents.
Suggested solution
Allow for including multiple YAML documents within a single file.
This would require a change in some interfaces that currently take a file URI and pass it down to be processed by specialized functions first and extracting a list of YAML documents.
Alternative
No response
Additional context
Here are two relevant links to YAML official specification
2.2 Structures
4.3.1 Document
Validations
next
version already [https://woodpecker-ci.org/versions]The text was updated successfully, but these errors were encountered: