Jenkins OpenShift Pipeline

In this post we will understand Jenkins OpenShift Pipeline i.e. How we can create Pipeline using Jenkins and OpenShift. We will try to understand in depth how one can use Jenkins and OpenShift for Continous Integration and Continuous Deployment.

We will be using existing Jenkins assembly for Continuous Integration and OpenShift for Continuous Deployment.

CI-CD Pipeline
CI-CD Pipeline

I’ve create above diagram for the reference, Let us try to understand how this assembly will work for CI-CD Using Jenkins and OpenShift.


  2. Jenkins Master and Jenkins Slave Machine.
  3. Ansible Master as Jenkins Slave 2.
  4. Nexus Repository Manager.
  5. OpenShift

Connect Jenkins Slave -1 and Ansible Control Server as Jenkins Slave – 2 to Jenkins Master, Jenkins Slave – 1 and Nexus Server should be node to Ansible Control Server (Jenkins Slave – 2).

Step 1: Developer will commit the code to GIT, So it’s GIT where your all code will be stored.

Step 2: Jenkins will Pull code from GIT and build in one of the SLAVE associated with Jenkins where code will be build.

Step 3: Now Jenkins will call Ansible Control Server i.e. Slave – 2 and Ansible Playbook will pull the artifacts from Jenkins -Slave 1 and copy them in Nexus server.

Step 4: Now Ansible Playbook will copy artifacts and related files to OpenShift.

Step 5: Write the command which you want to execute on OpenShift and your application will be deployed.

This is the complete CI-CD Using Jenkins, Ansible, Nexus and OpenShift. In the next post we will be implementing the complete CI-CD Pipeline where we will be writing Jenkinsfile, yaml file for OpenShift container, Playbook for ansible and many more stuff to automate this.

Do let me know in the comment section if you’ve any queries or suggestion.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s