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

Testing Matrix #1826

Open
vdemeester opened this issue Nov 3, 2023 · 0 comments
Open

Testing Matrix #1826

vdemeester opened this issue Nov 3, 2023 · 0 comments
Labels
area/release Indicates an issue on release (process, tasks). area/testing Issues or PRs related to testing kind/feature Categorizes issue or PR as related to a new feature.

Comments

@vdemeester
Copy link
Member

vdemeester commented Nov 3, 2023

The operator should be tested on a variety of Kubernetes version, from the lowest we support to the latest available.

We should nightly as well as on pull-requests (running them in parallel). Today, we only have one check which is pull-tekton-operator-integration-tests. Instead we should have several of them, one per k8s version we "support". We do not necessarily need to run the full test-suites on all version (if they are taking ages), but a selected number that should cover the basis (and most components if not all).

  • We can go the chains route and start by using GitHub workflows (and kind)
  • We can then (or initially) go the tekton+matrix routes and hook the dogfooding tekton cluster to this repository.

I would suggest we should go ahead with the GitHub workflow to work on the "tooling" to do this. Porting it to tekton then should be relatively straightforward.

cc @tektoncd/operator-maintainers

Note: e.g. tektoncd/chains is doing that on pull-request (like here)
2023-11-03-121630

@vdemeester vdemeester added kind/feature Categorizes issue or PR as related to a new feature. area/testing Issues or PRs related to testing area/release Indicates an issue on release (process, tasks). labels Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release Indicates an issue on release (process, tasks). area/testing Issues or PRs related to testing kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant