mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-26 08:10:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
CSI driver for Ceph
198 Commits 31 Branches 39 Tags 143 MiB
Go 95.1%
Shell 2.9%
Python 1%
Makefile 0.6%
Smarty 0.3%
Other 0.1%
69cb6aeead
Go to file
Niels de Vos 69cb6aeead ci: pre-pull ROOK_CEPH_CLUSTER_IMAGE if set 
After the introduction of ROOK_CEPH_CLUSTER_IMAGE in build.env, the
additional image needs to get pulled from the CI registry mirror and
pushed into the minikube VM.

Without this addition, the Docker Hub pull limits may prevent deploying
Rook.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-03-03 11:29:52 +00:00
deploy ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
jobs ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
scripts ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
.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: enable USE_PULLED_IMAGE to prevent image builds 2020-11-04 05:52:01 +00:00
commitlint.groovy ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
containerized-tests.groovy ci: prevent parallel builds from causing conflicts 2021-03-03 05:48:42 +00:00
k8s-e2e-external-storage.groovy ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
Makefile build: only use --cpuset options when the cgroup controller is available 2021-03-03 05:48:42 +00:00
mini-e2e-helm.groovy ci: pre-pull ROOK_CEPH_CLUSTER_IMAGE if set 2021-03-03 11:29:52 +00:00
mini-e2e.groovy ci: pre-pull ROOK_CEPH_CLUSTER_IMAGE if set 2021-03-03 11:29:52 +00:00
podman2minikube.sh ci: log output of "docker image save" 2020-12-01 16:52:41 +00:00
prepare.sh ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +00:00
README.md ci: update links to new OCP4 deployment 2020-07-24 14:11:42 +00:00
run-k8s-external-storage-e2e.sh ci: use self-contained kubeconfig for running k8s e2e job 2020-10-28 14:03:44 +00:00
single-node-k8s.sh ci: pre-pull ROOK_CEPH_CLUSTER_IMAGE if set 2021-03-03 11:29:52 +00:00
upgrade-tests.groovy ci: the "master" branch got renamed to "devel" 2021-03-01 05:22:06 +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.