OpenShift CI/CD Concepts

From NovaOrdis Knowledge Base
Jump to navigation Jump to search

External

Internal

Overview

This article aggregates concepts related to the implementation of CI/CD pipelines in OpenShift. OpenShift relies on Jenkins to execute the core pipeline logic - pipeline is a Jenkins concept. Thus, Jenkins instances are deployed and integrated with OpenShift. Details related to how to integrate Jenkins with OpenShift are discussed in the Jenkins Integration section. Jenkins pipelines are exposed natively in OpenShift as pipeline builds.

Jenkins Integration

https://github.com/openshift/jenkins

OpenShift Jenkins Plugins

Jenkins is ultimately the application that drives the pipeline logic so it first need to be told what to do, via its Groovy pipeline syntax, and then it needs to execute the actions, and while doing so, it needs to access and modify OpenShift resources. All these are implemented via a series of plugins, described below:

OpenShift Plugin for Jenkins (jenkins-plugin)

https://github.com/openshift/jenkins-plugin

This is the oldest Jenkins/OpenShift integration plugin, which executes inside Jenkins and implements a series of REST flows that interface with the OpenShift master server via its exposed API. This plugin does not require the oc binary to be present on the host that executes the plugin logic.

OpenShift Jenkins Pipeline Plugin (jenkins-client-plugin)

https://github.com/openshift/jenkins-client-plugin

jenkins-sync-plugin

https://github.com/openshift/jenkins-sync-plugin

jenkins-openshift-login-plugin

https://github.com/openshift/jenkins-openshift-login-plugin

Deplete

tmp