Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement parameter-conditioned gating #43

Open
rplevka opened this issue Jan 11, 2024 · 1 comment
Open

Implement parameter-conditioned gating #43

rplevka opened this issue Jan 11, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@rplevka
Copy link

rplevka commented Jan 11, 2024

What feature do you want to see added?

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

@rplevka rplevka added the enhancement New feature or request label Jan 11, 2024
@olivergondza
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants