Skip to content

CentOS CI - On-boarding

CentOS CI - On-boarding

  1. Create an entry in duffy db (with ssh key) - follow
  2. Create an OpenShift namespace/project (done with ansible)
  3. Create a PV(Persistent Volume) and deploy Jenkins instance (done with ansible)
Create an entry in duffy db (with ssh key) - follow
Create an OpenShift namespace


It's all created automatically now, including groups/users membership, and tied to ACO/FAS. The only needed operation is to create in IPA a group with suffix ocp-cico- and then name of the group/project. So for example create ocp-cico-kmods group, itself nesting sig-kmods and so existing users. Maximum 2 minutes later, the project/group should be created automatically in openshift cluster

Deploy a PV (Persistent Volume) and Jenkins instance


In case you just need to create a PV outside of jenkins, follow Persistent storage via NFS.

We have an ad-hoc ansible task (adhoc-ocp-deploy-jenkins-for-ci-tenant.yml) that will create the needed PV , create a template and apply it with the correct ssh keys and duffy api key so ensure that you followed previous steps so that you have the project keys into pkistore git repo (using project name) and also duffy api key ready (as script will ask you for it):

ansible-playbook-ci playbooks/adhoc-ocp-deploy-jenkins-for-ci-tenant.yml

Just answer the following questions (project has to exist first ! :

Existing project/namespace in ocp we'll deploy jenkins to/for (has to exist before !) : samba
Persistent Volume size (example 10Gi) : 10Gi
Existing Duffy API key : <duffy_api_key>

Now you just have to wait for jenkins to be up and running


We recently had an issue with the default jenkins image having outdated (and not working) openshift sync plugin so be sure that you have at least 1.0.51 running in openshift. If not, update it first, and then configmap will be synced to jenkins, for the cico-workspace pod template