Chapter 4. Pipelines
The Job of the deployment pipeline is to prove that the release candidate is unreleasable.
Jez Humble
Pipelines allow teams to automate and organize all of the activities required to deliver software changes. By rapidly providing visible feedback, teams can respond and react to failures quickly.
In this chapter we are going to learn about using pipelines inside OpenShift so that we can connect deployment events to the various upstream gates and checks that need to be passed as part of the delivery process.
Our First Pipeline Example
Log in to OpenShift as our user and create a new project. We will follow along using both the web-ui and the command-line interface (choose whichever one you’re most comfortable using):
$ oc login -u developer -p developer
Create a new project called samplepipeline:
$oc new-project samplepipeline --display-name="Pipeline Sample"\--description='Pipeline Sample'
Add the Jenkins ephemeral templated application to the project—it should be an instant app in the catalog which you can check from the web-ui by using Add to Project or from the CLI:
$oc get templates -n openshift|grep jenkins-pipeline-example jenkins-pipeline-example This example showcases the new Jenkins Pipeline ...
If you have persistent storage and you want to keep your Jenkins build logs after Jenkins Container restarts, then you could use the jenkins-persistent template instead.
$ oc new-app jenkins-ephemeral
In the web-ui continue to the overview page. A ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access