mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-09-19 23:19:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
CSI driver for Ceph
101 Commits 25 Branches 38 Tags 164 MiB
Go 94.9%
Shell 2.9%
Python 1%
Makefile 0.7%
Smarty 0.3%
Other 0.2%
73244ab07b
Go to file
Niels de Vos 73244ab07b ci: add script to detect latest Kubernetes patch release 
By using this script, we can pass Kubernetes versions like v1.19 to the
CI jobs. The jobs are then responsible for detecting the a full release
version, including the '.patch' suffix.

Versions are passed as 1.19, releases have the 'v' prefix as in v1.19.1.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-09-15 17:02:04 +05:30
deploy ci: OCP4 deletes pods from batch jobs automatically 2020-07-24 14:11:42 +00:00
jobs ci: update kubernetes version for e2e job 2020-09-09 14:02:45 +00:00
scripts ci: add script to detect latest Kubernetes patch release 2020-09-15 17:02:04 +05:30
.commitlintrc.yml ci: error out for invalid component in commit header 2020-08-19 11:15:09 +00: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: the ci-job-validation script uses an undefined variable 2020-08-13 18:56:41 +05:30
commitlint.groovy ci: fetch full history when cloning for commitlint job 2020-08-18 11:54:23 +00:00
containerized-tests.groovy ci: skip containerized-tests for doc-only PRs 2020-08-12 16:04:26 +00:00
Makefile ci: use FETCH_HEAD like "commitlint --from" does 2020-08-18 11:54:23 +00:00
mini-e2e-helm.groovy ci: skip mini-e2e-helm jobs if PR has the 'ci/skip/e2e' label 2020-08-24 08:51:46 +00:00
mini-e2e.groovy ci: skip mini-e2e jobs if PR has the 'ci/skip/e2e' label 2020-08-24 08:51:46 +00:00
prepare.sh ci: prepare.sh should accept --history without argument 2020-08-18 15:00:17 +02:00
README.md ci: update links to new OCP4 deployment 2020-07-24 14:11:42 +00:00
single-node-k8s.sh rebase: use Rook v1.3.9 for mini-e2e jobs 2020-08-17 03:44:37 +00:00

README.md

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.