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

Add enable-api-fields: alpha to pipeline's CI runs #3896

Closed
ghost opened this issue Apr 23, 2021 · 1 comment · Fixed by #3917
Closed

Add enable-api-fields: alpha to pipeline's CI runs #3896

ghost opened this issue Apr 23, 2021 · 1 comment · Fixed by #3917
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@ghost
Copy link

ghost commented Apr 23, 2021

Feature request

Once #3881 is merged we'll be in a good position to start testing alpha fields in our CI. In order to exercise new alpha features we'll need to add an additional round of integration tests and example runs in a cluster with enable-api-fields: alpha set in the feature-flags configmap.

Use case

Contributors to Tekton Pipelines should be able to observe the effects of their changes in environments with both "alpha" and "stable" feature gates during CI runs.

@ghost ghost added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 23, 2021
@pritidesai pritidesai added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 5, 2021
@pritidesai
Copy link
Member

thanks @sbwsg yup, we need this to validate any new alpha features being added. I have bumped up the priority for the same reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant