-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
Pipelines Sprint Release 16
Story (Required)
As a QE, I want to verify addon tasks shipped with operator, similarly to cluster tasks.
Background (Required)
We have automated tests for shipped cluster tasks in https://github.com/openshift-pipelines/release-tests/tree/master/specs/clustertasks
Extend the test suite in release-tests repo to include tests also for ecosystem tasks + cluster resolver.
docs: https://github.com/openshift/openshift-docs/pull/77342
Approach (Required)
1. Create new test for the following tasks using a cluster resolver
2. Extend addon tests to check that disabling/enabling the addon works as expected
3. Add a new task to main pipelines - acceptance-tests, upgrade-tests and cluster-upgrade-tests
$ oc get task -n openshift-pipelines NAME AGE buildah 6h14m git-cli 6h14m git-clone 6h14m maven 6h14m openshift-client 6h14m s2i-dotnet 6h14m s2i-go 6h14m s2i-java 6h14m s2i-nodejs 6h14m s2i-perl 6h14m s2i-php 6h14m s2i-python 6h14m s2i-ruby 6h14m skopeo-copy 6h14m tkn 6h14m
Additionally, we might consider removing original cluster resolver tests.
- relates to
-
SRVKP-5553 [Downstream CI] use resolver + addon instead of cluster tasks in CI pipelines
- Closed
-
SRVKP-5871 [Downstream CI] run s2i tests in parallel
- Closed
- mentioned on