What is Continuous Integration in Jenkins - Visual Explanation

Process Flow - What is Continuous Integration

Developer writes code

↓

Push code to shared repo

↓

CI server detects change

↓

Run automated build & tests

↓

Report results

↓

Fix issues if any

↓

Repeat

Continuous Integration means developers regularly add code to a shared place, where automated tools build and test it to catch problems early.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

A simple Jenkins pipeline that runs a build step when code is pushed.

Process Table

Step	Action	Trigger	Result	Next Step
1	Developer writes code	Manual	Code ready locally	Push code to repo
2	Push code to shared repo	Manual	Code updated in repo	CI server detects change
3	CI server detects change	Repo update event	Start build and tests	Run build stage
4	Run build stage	CI pipeline	Build successful or failed	Report results
5	Report results	Build completion	Notify developer	Fix issues if any
6	Fix issues if any	Developer action	Code fixed locally	Push code to repo
7	Repeat cycle	Continuous process	Code quality improves	Continuous Integration

💡 Process repeats continuously as developers push new code.

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
Code State	Local changes	Pushed to repo	Built and tested	Fixed and ready	Integrated in main branch
Build Status	N/A	N/A	Success or Fail	N/A	Success after fixes

Key Moments - 2 Insights

Why does the CI server start a build automatically after code is pushed?

Because the CI server listens for changes in the shared repo (see execution_table step 3), it triggers the build to catch errors early.

What happens if the build or tests fail?

The CI server reports the failure to the developer (step 5), so they can fix the code and push again (step 6).

Visual Quiz - 3 Questions

Look at the execution table, what triggers the CI server to start the build?

A Developer writes code locally

B Push code to shared repo

C Build stage completes

D Developer fixes issues

💡 Hint

Check step 3 in the execution_table where the CI server detects repo changes.

At which step does the developer get notified about build results?

A Step 5

B Step 4

C Step 2

D Step 6

💡 Hint

Look at the 'Report results' action in step 5 of the execution_table.

If the build fails, what is the next action according to the flow?

A Push code to repo again

B Run tests again automatically

C Fix issues locally

D Exit the process

💡 Hint

See step 6 where the developer fixes issues after notification.

Concept Snapshot

Continuous Integration (CI) means developers frequently push code to a shared repo.
A CI server detects changes and runs automated builds and tests.
If tests fail, developers fix code and push again.
This cycle helps catch errors early and keeps code healthy.
Jenkins pipelines automate this process with stages like build and test.

Full Transcript

Continuous Integration is a practice where developers regularly add their code to a shared repository. When code is pushed, a CI server like Jenkins detects the change and automatically runs build and test steps. The results are reported back to the developer. If there are problems, the developer fixes the code and pushes again. This cycle repeats continuously to keep the codebase stable and errors caught early.