What is CI/CD?

CI/CD in Jenkins refers to the automation of software delivery phases using the Jenkins automation server. Continuous Integration (CI) focuses on automatically building and testing code changes, while Continuous Delivery/Deployment (CD) ensures those changes are reliably delivered to staging or production environments.

The Two Core Components

Continuous Integration (CI):
- Automates code merging.
- Triggers automatic builds.
- Runs instant tests.
- Catches bugs early.
Continuous Delivery / Deployment (CD):
- Automates the release process.
- Delivers to staging environments (Delivery).
- Deploys directly to production (Deployment).
- Reduces manual human errors.

Simple Definition: Continuous Integration and Continuous Delivery/Deployment automate the path from source-code change to a tested and releasable application.

Key Concepts

Concept

Understand the purpose of What is CI/CD? and how it fits into a Jenkins workflow.

Real-World Use

Apply the concept when creating, running, testing, or deploying a Jenkins job or pipeline.

Practical Jenkins Example

pipeline {
    agent any
    stages {
        stage('Learn What is CI/CD?') {
            steps {
                echo 'Jenkins lesson: What is CI/CD?' 
            }
        }
    }
}

Practice Exercise

Open Jenkins and identify the relevant configuration area.
Create or update a small test job or pipeline for this lesson.
Run the job and inspect the Console Output.
Record what changed and verify the result.

Summary

You have completed the What is CI/CD? lesson. Continue through the syllabus to build the Jenkins skills required for real CI/CD automation.

← Previous: Introduction to Jenkins Next: Why Jenkins? →