Tutorial - Jenkins CI/CD Pipeline

Create an Immutable Kubernetes Environment for Your CI/CD Pipeline

The secret to the success of any DevOps initiative is a stable CI/CD pipeline. CI – or Continuous Integration – involves automatically taking newly-merged code and then building, testing, and depositing that code in an artifact repository. CD – Continuous Deployment – involves taking that freshly-deposited artifact and deploying it into a production environment.

In this tutorial, we’re going to build the infrastructure for a CI/CD pipeline in our Kubernetes environment. A successful merge to the master branch in a GitHub project will trigger a Jenkins 2 pipeline, which can build, test and deploy an updated project into our environment.

In addition to GitHub and Jenkins, we’ll be making use of a private JFrog repository to store the image for our pipeline, and we’ll be deploying everything on a cluster managed with Platform9’s Managed Kubernetes Services - Freedom platform.

Follow the guide at https://docs.platform9.com/kubernetes/tutorials/cicd-pipeline-on-kubernetes/