CSI driver for Ceph
Go to file
Praveen M 3e6791171d ci: e2e job for ceph-csi operator
This commit adds new job mini-e2e-operator for running
ceph-csi e2e tests deployed via ceph-csi-operator.

Signed-off-by: Praveen M <m.praveen@ibm.com>
2024-10-29 15:32:49 +05:30
deploy ci: only update jobs, do not check views 2024-08-07 10:05:07 +00:00
jobs ci: e2e job for ceph-csi operator 2024-10-29 15:32:49 +05:30
mirror ci: update ceph image 2024-07-26 09:09:09 +00:00
scripts ci: use Helm 3.1.2 in test container 2021-04-20 07:08:16 +00:00
.commitlintrc.yml ci: error out for invalid component in commit header 2020-08-19 11:15:09 +00:00
.gitignore cleanup: add unwanted files to gitignore 2022-05-05 09:44:57 +00:00
build-images.groovy ci: move inline script into separate build-images.groovy file 2024-01-30 17:43:25 +01:00
ci-job-validation.groovy ci: use CentOS 9 Stream machines for all Jenkins jobs 2024-05-29 16:53:57 +02:00
commitlint.groovy ci: use CentOS 9 Stream machines for all Jenkins jobs 2024-05-29 16:53:57 +02:00
containerized-tests.groovy ci: use quay.io for ceph image 2024-07-30 07:42:46 +00:00
jjb-deploy.groovy ci: replace inline dsl: script by Groovy files 2024-01-31 09:54:41 +01:00
jjb-validate.groovy ci: replace inline dsl: script by Groovy files 2024-01-31 09:54:41 +01:00
k8s-e2e-external-storage.groovy ci: use quay.io for ceph image 2024-07-30 07:42:46 +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: use quay.io for ceph image 2024-07-30 07:42:46 +00:00
mini-e2e-operator.groovy ci: e2e job for ceph-csi operator 2024-10-29 15:32:49 +05:30
mini-e2e.groovy ci: use quay.io for ceph image 2024-07-30 07:42:46 +00:00
podman2minikube.sh ci: copy images into minikube container when VM_DRIVER=podman 2022-10-12 10:14:49 +00:00
prepare.sh ci: install wget for downloading Helm 2022-10-13 06:26:56 +00:00
README.md doc: Update/remove broken links 2023-07-04 14:58:17 +00:00
run-k8s-external-storage-e2e.sh ci: update path for kubernetes-test-linux 2024-09-12 09:40:33 +00:00
single-node-k8s.sh ci: use VM_DRIVER=podman for AWS virtual-machines 2022-10-10 07:18:28 +00:00
system-status.sh ci: add sudo prefix for status commands 2023-08-24 11:14:11 +00:00
upgrade-tests.groovy ci: use quay.io for ceph image 2024-07-30 07:42:46 +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 duffy (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.