E2E tests were running an older version of pipelines ie v0.45.0.
Bumping it to use the latest version v0.51.0 so that current tasks in
catalog can be tested against latest version
Also remove pipelineresources check while doing installation of latest
version of pipelines
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
This commit updates the catalog e2e tests to use the latest Pipelines release.
Because this release removes support for v1alpha1 Task, TaskRun, Pipeline, and
PipelineRun, and the previous release removes support for Conditions, this
commit also updates tests to use up-to-date versions of Tekton CRDs.
It does not update any catalog Tasks or Pipelines.
Since the no of resources in catalog are increasing, the whole test
suite is taking more time so increasing the parallel run from 5 -> 8
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
Prior to this commit we were using Pipelines 0.28 for running e2e tests
in the Catalog.
This commit updates the pipelines version used during testing to 0.32.0,
which was released today.
After making this change one of the steps in an Orka Task is now failing
due to a naming conflict. This commit also renames the step to work
around the issue.
PLATFORM env variable is introduced. This variable allows to run
tests for specific platform (for insance, "linux/s390x" or "linux/ppc64le").
If the environment variable is specified
- some tests are updated with different image values/other parameter
values, required for specific platform, using yq tool.
Custom values should be specified in the script file, separate for each
platform. In the current code script file for linux/s390x is proposed.
- only tasks, which have mention about corresponding platform support
in the annotation, will be tested.
If PLATFORM env variale is no specified, the behaviour of test scripts
will be similar to the one before the PR.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
The image is used in many catalog tests. To run the tests on many
platforms, the image should be the multi-arch one (at this moment -
linux/amd64, linux/ppc64le, linux/s390x, linux/arm64).
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
When adding `fixtures` volume, we need to consider whether the task
already has a volumes section. If the volumes is already defined, then
we should add `fixtures` rather than replacing the whole volumes.
The regexp was catching up golang-test/ task so it will always test
everything when there is in golang-test/
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
As of now the function `detect_changed_e2e_test` was running even if the
variable `TEST_RUN_ALL_TESTS` value was set which resulted in breaking
the CI.
Add a condition to call the function iff `TEST_RUN_ALL_TESTS` value is
not set.
Signed-off-by: vinamra28 <vinjain@redhat.com>
As of now if there is some modification in any e2e test then CI doesn't
run on whole catalog and this might result in failure of some task which
we get to know next day whene nightly periodic job runs.
This change detects the changes in the tests dir and if there is any
change then run the CI on whole catalog.
Signed-off-by: vinamra28 <vinjain@redhat.com>
In e2e tests script podTemplate was getting added even if the yaml
manifest contains only ConfigMap which was failing the CI.
Append volumes in sidecar to mount fixtures ConfigMap instead of using podTemplate
as appending the podTemplate was conditional and there can be scenarios
where podTemplate might get appended at wrong location.
Signed-off-by: vinamra28 <vinjain@redhat.com>
- Check for libraries in a pip agnostic way
- allow for adding multiple sidecars with a reusable `add_sidecars` function
- fix overwriting sidecars issue for previous python
- make it more readable
Extend to test logic to be able to load the fixture reponse from a
file, so that we don't have to inline a long JSON doc into the fixture
config YAML. This is achieved by creating a config map with all the
files in the fixtures folder, and mounting that configmap as a volume
to the sidecar.
This allows improving the test for the github-add-comment task v0.4
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
If a task is being removed from the catalog then also the CI runs the
check for validating the YAML and thus fails if the task manifest is not
found.
This PR checks for the task directory whether it exists or not and in the case
where task directory is not present then the function doesn't checks the
validation of the YAML. Example if we remove the task knctl-deploy then
the CI would skip the check for that pull request.
Signed-off-by: vinamra28 <vinjain@redhat.com>
The e2e tests detect changes in subdir but also applies that
subdir while testing which fails the tests for some new PRs such as
This PR detects changes even in subdir but only passes the valid test
dir path to the script and avoid subdirs such as /mods, /mocks etc
Signed-off-by: vinamra28 <vinjain@redhat.com>
e2e script was unable to detect the changes in the `pre-apply-task-hook.sh` file(if any)
and was checking only file changes in YAML files. Fixed!
Signed-off-by: vinamra28 <vinjain@redhat.com>
Currently no of parallel tasks running at a time are 5
but in case the last set of tasks doesn't count upto 5
then handling that case over here.
Signed-off-by: vinamra28 <vinjain@redhat.com>
In some case we want to be able to redefine the KUBECONFIG commands, when other
CI needs to redefines it.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
We were running previously the tests sequentially,
Since the catalogs tests are growing exponentially, let's add parallelization to
speed things up.
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Current e2e script is only able to run integration tests on those PRs which include tests.
With this fix, tests will run on those PRs also in which only task yaml is changed
Signed-off-by: vinamra28 <vinjain@redhat.com>
