CI/CD tools landscape in Jenkins - Step-by-Step Execution

Process Flow - CI/CD tools landscape

Code Commit

↓

Trigger CI Server

↓

Build & Test

↓

If Tests Pass?

No→Notify Failure

Yes↓

Deploy to Staging

↓

Manual or Auto Approval?

No→Wait

Yes↓

Deploy to Production

↓

Notify Success

This flow shows how code changes trigger automated build, test, and deployment steps with checks and notifications.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') { steps { echo 'Building...' } }
    stage('Test') { steps { echo 'Testing...' } }
    stage('Deploy') { steps { echo 'Deploying...' } }
  }
}

A simple Jenkins pipeline that runs build, test, and deploy steps in order.

Process Table

Step	Action	Stage	Output	Next Step
1	Start pipeline	N/A	Pipeline started	Build stage
2	Run build	Build	Building...	Test stage
3	Run tests	Test	Testing...	Deploy stage
4	Run deploy	Deploy	Deploying...	Pipeline complete
5	End pipeline	N/A	Pipeline finished successfully	Exit

💡 Pipeline completes after deploy stage with success notification.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
pipeline_status	Not started	Building	Testing	Deploying	Success

Key Moments - 2 Insights

Why does the pipeline stop if tests fail?

The pipeline checks test results after the Test stage (see step 3 in execution_table). If tests fail, it triggers failure notification and stops to prevent bad code deployment.

What triggers the deployment stage?

Deployment runs only after successful tests (step 4 in execution_table). This ensures only verified code is deployed.

Visual Quiz - 3 Questions

Look at the execution table, what is the pipeline_status after Step 3?

A Testing

B Building

C Deploying

D Success

💡 Hint

Check variable_tracker column 'After Step 3' for pipeline_status.

At which step does the pipeline finish successfully?

A Step 3

B Step 4

C Step 5

D Step 2

💡 Hint

Look at execution_table row with 'Pipeline finished successfully' output.

If tests fail at Step 3, what would happen next?

A Proceed to Deploy stage

B Notify failure and stop pipeline

C Restart Build stage

D Skip Test stage

💡 Hint

Refer to key_moments explanation about pipeline stopping on test failure.

Concept Snapshot

CI/CD pipelines automate code build, test, and deployment.
Code commit triggers pipeline start.
Build and test stages verify code.
Deploy stage runs only if tests pass.
Failures stop pipeline and notify team.
Jenkins pipelines define these steps in stages.

Full Transcript

This visual execution shows a Jenkins CI/CD pipeline flow. When code is committed, the pipeline starts and runs the Build stage, outputting 'Building...'. Next, it runs the Test stage with 'Testing...'. If tests pass, it proceeds to Deploy stage with 'Deploying...'. Finally, the pipeline finishes successfully. Variables track pipeline status changing from Not started to Building, Testing, Deploying, and Success. Key moments clarify that the pipeline stops if tests fail to avoid deploying bad code. The visual quiz checks understanding of pipeline status at steps and behavior on test failure.