Continuous Integration/Continuous Deployment Pipelines

Site: Digital Learning Portal

Course: IBM Cloud Private Continuing Education Series: Continuous Integration/Continuous Deployment Pipelines
Book: Continuous Integration/Continuous Deployment Pipelines
Printed by: Rajendra Kumar Bhandari
Date: Wednesday, November 6, 2019, 10:46 PM
Table of contents
1. Big picture: Build/Ship/Run

2. Interactive simulation: Use your Jenkins environment to continuously integrate and deliver on IBM Cloud Private
1. Big picture: Build/Ship/Run
The theory behind a deployment pipeline, often referred to as a build pipeline or staged build, is that there are  multiple builds done in
sequence. The commit to the mainline triggers the first build, also known as the commit build. The commit build is needed when someone
commits to the mainline. The commit build is done quickly and as a result takes a number of shortcuts that reduce the ability to detect
bugs. There is a balance to finding bugs and speed so that a good commit build is stable enough for other developers to use.  Once the
commit build is considered "good" then other people can work on the code with confidence.

The deployment pipeline's purpose is to detect any changes that lead to production problems. These can include performance, security, or
usability issues. A deployment pipeline should enable collaboration between the various groups involved in delivering software and
provide everyone visibility about the flow of changes in the system, together with a thorough audit trail.
2. Interactive simulation: Use your Jenkins environment to continuously
integrate and deliver on IBM Cloud Private

Simulation overview
Although using Jenkins inside a Kubernetes cluster is convenient, you might want to integrate the process of deploying an application to
IBM Cloud Private within your Jenkins environment.  In this interactive simulation, you learn how to install Jenkins in a Docker container
outside of the IBM Cloud Private Kubernetes environment.

This simulation has six main tasks:

1. Deploy a Jenkins server

2. Install kubectl on the Jenkins server
3. Install Helm on the Jenkins server
4. Obtain the Kubernetes client configuration from IBM Cloud Private
5. Configure the build process in Jenkins
6. Deploy an application from Jenkins

Access and begin the simulation

An interactive simulation allows you to perform tasks as if you were working in an actual environment without configuring the
environment. You will interact with tools needed for a CI/CD pipeline (Kubernetes, IBM Cloud Private, Helm, and Jenkins).

Click here to start the interactive simulation.  The simulation will open in a new window.  Close the window when you complete the
simulation.