674b1e811a
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>
Continuous Integration Jobs for the CentOS CI
- dedicated Jenkins instance for Ceph-CSI
- Jenkins is hosted on OpenShift in the CentOS CI
- Scripts and Jenkins jobs are hosted in the Ceph-CSI repository (ci/centos branch)
- A Jenkins Pipeline is used to reserve bare metal system(s), and run jobs on those systems
Repository/Branch Structure
This is the ci/centos branch, where all the scripts for the Jenkins jobs are
maintained. The tests that are executed by the jobs are part of the normal
projects branches.
As an example, the containerized-tests Jenkins job consists out of the
following files:
-
jobs/containerized-tests.yamlis a Jenkins Job Builder configuration that describes the events when the job should get run and fetches the.groovyfile from the git repository/branch -
containerized-tests.groovyis the Jenkins Pipeline that contains the stages for the Jenkins Job itself. In order to work with the bare-metal machines from the CentOS CI, it executes the following stages:- Dynamically allocate a Jenkins Slave (
node('cico-workspace')) with tools and configuration to request a bare-metal machine - Checkout the
centos/cibranch of the repository, which contains scripts for provisioning and preparing the environment for running tests - Reserve a bare-metal machine with
duffy(configured on the Jenkins Slave) - Provision the reserved bare-metal machine with additional tools and
dependencies to run the test (see
prepare.shbelow) - Run
make containerized-testsandmake containerized-buildin parallel - As final step, return the bare-metal machine to the CentOS CI for other users (it will be re-installed with a minimal CentOS environment again)
- Dynamically allocate a Jenkins Slave (
-
prepare.shinstalls dependencies for the test, and checks out the git repository and branch (or Pull Request) that contains the commits to be tested (and the test itself)
Deploying the Jenkins Jobs
The Jenkins Jobs are described in Jenkins Job Builder configuration files and
Jenkins Pipelines. These need to be imported in the Jenkins instance before
they can be run. Importing is done with the jenkins-jobs command, which runs
in a jjb container. To build the container, and provide the configuration for
Jenkins Job Builder, see the documentation in the deploy/
directory.