CSI driver for Ceph
Go to file
Niels de Vos 120bbc66ab ci: add commitlint fallback job
Each PR gets tested by the commitlint app (which is deprecated). On
occasion the app does not pickup the change in a PR, and the only way to
start a retest is to re-push the PR. All tests will then get executed
again, even if only commitlint was needed.

The new commitlint CI job introduces '/retest commitlint' and runs in
the CentOS CI like other Jenkins jobs. However, the job does not start
automatically on each (updated) PR, but needs manual starting with the
'/test commitlint' or '/retest commitlint' comments. The normal way of
running commitlint is with the app (at least for now).

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-08-07 12:52:05 +00:00
deploy ci: OCP4 deletes pods from batch jobs automatically 2020-07-24 14:11:42 +00:00
jobs ci: add commitlint fallback job 2020-08-07 12:52:05 +00:00
scripts ci: add 'make test' target to validate CI job scripts 2020-05-27 12:52:21 +02:00
.commitlintrc.yml ci: add 'make test' target to validate CI job scripts 2020-05-27 12:52:21 +02:00
.gitignore ci: add 'make test' target to validate CI job scripts 2020-05-27 12:52:21 +02:00
ci-job-validation.groovy ci: request CentOS-8 bare-metal machines 2020-08-01 11:24:35 +05:30
commitlint.groovy ci: add commitlint fallback job 2020-08-07 12:52:05 +00:00
containerized-tests.groovy ci: request CentOS-8 bare-metal machines 2020-08-01 11:24:35 +05:30
Makefile ci: add 'make test' target to validate CI job scripts 2020-05-27 12:52:21 +02:00
mini-e2e-helm.groovy ci: pass strings with quotes over ssh in mini-e2e-helm 2020-08-05 12:32:32 +00:00
mini-e2e.groovy ci: Correct the stage name 2020-08-04 04:02:18 +00:00
prepare.sh ci: use dnf on CentOS-8 systems 2020-08-03 08:11:17 +00:00
README.md ci: update links to new OCP4 deployment 2020-07-24 14:11:42 +00:00
single-node-k8s.sh ci: give minikube 8GB RAM on CentOS bare-metal systems 2020-08-04 07:19:39 +00:00

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.yaml is a Jenkins Job Builder configuration that describes the events when the job should get run and fetches the .groovy file from the git repository/branch

  • containerized-tests.groovy is 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:

    1. dynamically allocate a Jenkins Slave (node('cico-workspace')) with tools and configuration to request a bare-metal machine
    2. checkout the centos/ci branch of the repository, which contains scripts for provisioning and preparing the environment for running tests
    3. reserve a bare-metal machine with cico (configured on the Jenkins Slave)
    4. provision the reserved bare-metal machine with additional tools and dependencies to run the test (see prepare.sh below)
    5. run make containerized-tests and make containerized-build in parallel
    6. 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)
  • prepare.sh installs 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.