mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-10 00:10:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
CSI driver for Ceph
7 Commits 24 Branches 38 Tags 140 MiB
Go 95.1%
Shell 2.9%
Python 1%
Makefile 0.6%
Smarty 0.3%
Other 0.1%
917ec1e2f1
Go to file
Yug Gupta 917ec1e2f1 prepare: exit when passed incorrect parameters 
Now script does not continue execution
when an invalid argument is passed.

Signed-off-by: Yug Gupta <ygupta@redhat.com>
2020-05-07 10:31:57 +02:00
deploy add scripts and configuration to deploy with Jenkins Job Builder 2020-04-01 14:15:04 +02:00
jjb-deploy.yaml add jjb-<cmd> jobs for validating/deploying Jenkins jobs 2020-04-01 14:15:04 +02:00
jjb-validate.yaml add jjb-<cmd> jobs for validating/deploying Jenkins jobs 2020-04-01 14:15:04 +02:00
make-containerized-build.groovy add make-containerized-build job 2020-04-01 14:15:04 +02:00
make-containerized-build.yaml ci: add xterm logging wrapper and timestamps 2020-04-06 09:54:33 +02:00
prepare.sh prepare: exit when passed incorrect parameters 2020-05-07 10:31:57 +02:00
README.md add make-containerized-build job 2020-04-01 14:15:04 +02: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 make-containerized-build Jenkins job consists out of the following files:

  • make-containerized-build.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

  • make-containerized-build.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 the test
    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.