OpenShift CI/CD Concepts: Difference between revisions
Line 17: | Line 17: | ||
=OpenShift Jenkins Plugins= | =OpenShift Jenkins Plugins= | ||
Jenkins is ultimately the application that drives the pipeline logic so it needs to know how to access and modify OpenShift resources. It does so via a series of plug-ins, as follows: | |||
* | |||
* | |||
* | |||
Revision as of 17:34, 8 December 2017
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
OpenShift Jenkins Plugins
Jenkins is ultimately the application that drives the pipeline logic so it needs to know how to access and modify OpenShift resources. It does so via a series of plug-ins, as follows:
https://github.com/openshift/jenkins-client-plugin
https://github.com/openshift/jenkins-plugin
https://github.com/openshift/jenkins-sync-plugin
https://github.com/openshift/jenkins-openshift-login-plugin