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
d8a619a743
ceph-csi/deploy
History
Niels de Vos 6e38694a11 ci: the order of --allow-empty-variables for jenkins-jobs is important 
Jenkins Jobs Builder fails like this, indicating the order of the
parameters is important:

```
$ jenkins-jobs update --allow-empty-variables --delete-old jobs
usage: jenkins-jobs [-h] [--conf CONF] [-l LOG_LEVEL] [--ignore-cache]
                    [--flush-cache] [--version] [--allow-empty-variables]
                    [--server SECTION] [--user USER] [--password PASSWORD]
                    {delete,delete-all,get-plugins-info,list,test,update} ...
jenkins-jobs: error: unrecognized arguments: --allow-empty-variables
```

Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-01-30 18:14:58 +01:00
..
ceph-csi-buildconfig.yaml ci: migrate to new OpenShift cluster running on AWS 2023-03-20 09:21:41 +00:00
checkout-repo.sh ci: correct parameter passing in checkout-repo.sh 2023-03-20 09:21:41 +00:00
container-registry.yaml ci: migrate to new OpenShift cluster running on AWS 2023-03-20 09:21:41 +00:00
docker-gc.yaml ci: run registry garbage collection every week 2023-03-20 14:20:53 +00:00
Dockerfile build: remove urllib3 downgrade in jjb container, use timeout instead 2023-06-28 12:48:12 +00:00
jjb-buildconfig.yaml ci: fix yamllint issues in jjb-buildconfig.yaml 2020-05-27 12:52:21 +02:00
jjb-config.yaml build: remove urllib3 downgrade in jjb container, use timeout instead 2023-06-28 12:48:12 +00:00
jjb-deploy.yaml ci: set ttlSecondsAfterFinished=10 to ensure job status can be checked 2021-08-09 14:47:18 +00:00
jjb-validate.yaml ci: set ttlSecondsAfterFinished=10 to ensure job status can be checked 2021-08-09 14:47:18 +00:00
jjb.sh ci: deploy/jjb.sh should fail on wrong arguments 2020-11-04 10:09:57 +00:00
Makefile ci: the order of --allow-empty-variables for jenkins-jobs is important 2024-01-30 18:14:58 +01:00
README.md doc: Update/remove broken links 2023-07-04 14:58:17 +00:00

README.md

Deploying Jenkins Jobs through OpenShift

This deploy/ directory contains the configuration to prepare running Jenkins Job Builder on OpenShift and update/add Jenkins Jobs in an environment hosted in the same OpenShift project.

The used Jenkins environment is expected to be deployed already. This is done by the CentOS CI team when a request for CI resources is handled. The deploying and configuration of Jenkins is therefor not part of this document.

Building the Jenkins Job Builder container image

OpenShift has a feature called ImageStreams. This can be used to build the container image that contains the jenkins-jobs executable to test and update/add jobs in a Jenkins environment.

All .yaml files in this directory need to be pushed into OpenShift, use oc create -f <file> for that.

  • The Dockerfile uses pip to install jenkins-jobs, the BuildConfig object in OpenShift can then be used to build the image
  • checkout-repo.sh will be included in the container image, and checks out the ci/centos branch of the repository
  • Together with the Makefile (checked out with checkout-repo.sh), the Jenkins Jobs can be validated or deployed
  • jjb-buildconfig.yaml creates the ImageStream and the BuildConfig objects. Once created with oc create, the OpenShift Console shows a Build button for the jjb image under the Builds/Builds menu
  • jjb-config.yaml is the /etc/jenkins_jobs/jenkins_jobs.ini configuration files that contains username, password/token and URL to the Jenkins instance (edit this file before pushing to OpenShift)
  • jjb-validate.yaml is the OpenShift Job that creates a Pod, runs the validation test and exits. The job needs to be deleted from OpenShift before it can be run again.
  • jjb-deploy.yaml is the OpenShift Job that creates a Pod, runs jenkins-jobs to push the new jobs to the Jenkins environment. This pod uses the jjb-config ConfigMap to connect and login to the Jenkins instance. The job needs to be deleted from OpenShift before it can be run again.
  • jjb.sh is a helper script that can be used to validate/deploy the Jenkins Jobs in the parent directory. It creates the validate or deploy job, waits until the job finishes, shows the log and exits with 0 on success. This script can be used in Jenkins Jobs to automate the validation and deployment of jobs.