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
Currently there is no way to limit where to limit agents where pipelines without any filter labels specified to run on.
Suggested solution
Add configuration option for woodpecker server to set default label filters that would be set for pipelines that has no filter set.
This could also be used as alternative to fix #2634
Alternative
As workaround this possible be also implemented in external configuration service but that seems not so straightforward and could be harder to implement
Additional context
Gitlab CI implements similar approach to allow for agents to set option that they are allowed to run "untagged pipelines"
Validations
Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
lafriks
changed the title
Allow for woodpecker server to specify default filter labels
Allow configuration option to specify default filter labels
Nov 6, 2024
Clear and concise description of the problem
Currently there is no way to limit where to limit agents where pipelines without any filter labels specified to run on.
Suggested solution
Add configuration option for woodpecker server to set default label filters that would be set for pipelines that has no filter set.
This could also be used as alternative to fix #2634
Alternative
As workaround this possible be also implemented in external configuration service but that seems not so straightforward and could be harder to implement
Additional context
Gitlab CI implements similar approach to allow for agents to set option that they are allowed to run "untagged pipelines"
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: