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
My job is parametrized and only requires service foo if the build is executed with parameter use_foo: true.
Otherwise, it makes no sense to keep the build blocked on service foo unavailability.
I'd like to have a possibility to configure a conditioned gating service.
This might be implemented e.g. by specifying an optional job bool parameter to map a specific service to.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered:
This plugin (implementation) is a legacy one pending major rewrite: #44.
If such features are to be added, it will be done in gating-core, so other implementations can benefit from this.
It would be great if there were a way to expand parameter values in cachet requirements (at least for Jenkins pipeline job type), but I suspect it will not work because both parameters and cachet config are properties.
What feature do you want to see added?
My job is parametrized and only requires service
foo
if the build is executed with parameteruse_foo: true
.Otherwise, it makes no sense to keep the build blocked on service
foo
unavailability.I'd like to have a possibility to configure a conditioned gating service.
This might be implemented e.g. by specifying an optional job bool parameter to map a specific service to.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: