It seems that `${RUN_DISPLAY_URL}` is not expanded correctly in the
Jenkins Job Builder YAML files anymore. `$RUN_DISPLAY_URL` should be the
correct notation.
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Jenkins Jobs Builder does not like the inline `dsl:` scripts anymore, so
replace them by Groovy files in the main directory, similar to other
jobs.
Signed-off-by: Niels de Vos <ndevos@ibm.com>
The current e2e test runs will trigger all 3 types of
tests which takes a lot of time to complete. If the
patch impacta only a single type, then having an option
to trigger only that particular e2e test can save
considerable amount of time based on the test type.
This can also help in reducing the time in testing when
a patch failed on a particular e2e test type and triggering
only that e2e with the fix for the failure or re-trigger
only that test again to check for false positives.
Signed-off-by: karthik-us <ksubrahm@redhat.com>
The `/test ci/centos/mini-e2e-helm` has been broken with the last change
where `/test all` was removed. A remaining '(' makes the regular
expression invalid, and jobs fail to get started.
Fixes: f9f3bb9 ("ci: remove `/retest all` command for Jenkins jobs")
Signed-off-by: Niels de Vos <ndevos@ibm.com>
`/retest all` causes a spike in resource consumption in Jenkins and the
OpenShift cluster kills the Pod. That means tests are not fully running
yet, and results never arrive back in the PR. Instead of `/retest all`,
the `ok-to-test` label can be used to trigger required tests with a
slight delay between each command.
Signed-off-by: Niels de Vos <ndevos@ibm.com>
K8s 1.24 will be End of Life on 2023-07-28.
Therefore, this commit removes support
for k8s 1.24.
refer:
https://kubernetes.io/releases/#release-v1-24
Signed-off-by: Rakshith R <rar@redhat.com>
removed ability to run tests with
kubernetes 1.23 as its no longer
maintained version.
fixes: #3636
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Upgrade tests always runs with the latest
release of kubernetes, updating the
kubernetes to latest available release
in the CI.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Disable e2e tests by default in CI to
save resources. cephcsi maintainers or
contributors can add the ok-to-test label
to trigger the e2e tests.
depends on #3468
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
We will run CI on 3 latest kubernetes
releases removing Kubernetes 1.21 support
as we have Kubernetes 1.22, 1.23 and 1.24 for
CI Jobs.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
As we have stable CI for kubernetes v1.24 and
Kubernetes v1.24 released sometime back, defaulting
Kubernetes v1.24 for the CI run.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
This commits adds the kuberenetes
1.24 to run on request for now.
Note:- Once the kubernetes 1.24 job is stable
will run it by default
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
It seems that regular jobs in the OpenShift environment fail with the
following error:
Missing GOARCH argument for building image, install Golang or run: make containerized-test GOARCH=amd64
This happens for both the `devel` and `test` image builds since December
13 when installing Golang in the container-images was added.
Fixes: 8a3fe53e "ci: install arch specific go in Dockerfile.devel"
Signed-off-by: Niels de Vos <ndevos@redhat.com>
removing kubernetes test run with 1.20
as with #2705 we dont need 1.20 CI
results to merge a PR and we have kube 1.23
latest release.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
The e2e tests are running fine on kubernetes
1.23. This commit runs the tests on kubernetes
1.23 by default.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
This commits removes the older version (1.19
and 1.20) from testing and adds the kuberenetes
1.23 to run on request for now.
Note:- Once the kubernetes 1.23 job is stable
will run it by default
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
As kubernetes v1.19 is heading towards its EOL
on 2021-09-30, run tests on kubernetes v1.22
and require it to pass for merging.
Signed-off-by: Yug Gupta <yuggupta27@gmail.com>
Kubernetes 1.22 is in the release process and can be used for testing
already. The CI jobs will be available and can be triggered by leaving a
comment in the PRs like
/test ci/centos/mini-e2e-helm/k8s-1.22
See-also: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.22
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Kubernetes 1.21 is the latest stable release, and Ceph-CSI should be
tested with that. Currently 1.19 is still supported too, so we will need
to run the CI jobs with 1.19, 1.20 and 1.21.
See-also: https://kubernetes.io/releases/
Signed-off-by: Niels de Vos <ndevos@redhat.com>
When the `ci/centos` branch has been merged, the container images that
are built from it may need to be rebuilt. Instead of conditionally
rebuilding images only on a change, just rebuild them always, as there
are very few changes in the CI branch anyway.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
The Kubernetes e2e external storage tests from v1.21 do not work yet
with Ceph-CSI. In order to address the issues, the job is now provided
and can be run with:
/test ci/centos/k8s-e2e-external-storage/1.21
The job for v1.20 is enabled by default, and identified by the
ci/centos/k8s-e2e-external-storage/1.20 context in PRs.
Updates: #2017
Signed-off-by: Niels de Vos <ndevos@redhat.com>
To test a PR with Kubernetes 1.21, leave a comment in the PR like:
/test ci/centos/mini-e2e-helm/k8s-1.21
The status of the job will be recorded in the PR, but running this job
is not required (yet).
Updates: #1963
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Kubernetes v1.20 has been released, so lets use that for testing. Note
that v1.18 is still maintained, but our CI jobs will not consume it
anymore.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Add CI jobs for Kubernetes v1.20 testing. These jobs will run, but are
not (yet) required before changes get merged.
Updates: #1784
Signed-off-by: Niels de Vos <ndevos@redhat.com>
The commitlint job is not used normally, so there is no need to run it
when all CI jobs need retesting.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
As ${RUN_DISPLAY_URL} also matches the format for template
substitutions, it can not be used like this for all Jenkins Jobs Builder
files. Instead, $RUN_DISPLAY_URL can be used, as it does not have the
{curly_braces} format and the template engine skips it.
Fixes: 87870369 (ci: link to the job in the Blue Ocean webui)
Signed-off-by: Niels de Vos <ndevos@redhat.com>
The new Blue Ocean webui is much easier to navigate than the traditional
Jenkins webui. Developers that want to check failures of CI jobs will be
able to find the logs much quicker as each stage/step has a clear
success or failed status.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Because the parallel steps, the build.env is not in the local directory
where the command is executed. So fetch the BASE_IMAGE before continuing
with 'oc start-build', and pass the name of the image on the
commandline.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
