What is Continuous Integration in Jenkins - Hands-On Activity

What is Continuous Integration

📖 Scenario: You are working as a developer in a team. Your team wants to make sure that every change made to the code is tested automatically to avoid bugs. This helps the team deliver better software faster.

🎯 Goal: Learn the basic concept of Continuous Integration (CI) by setting up a simple Jenkins pipeline that runs a test command automatically whenever code changes are made.

📋 What You'll Learn

Create a Jenkins pipeline script with a basic structure

Add a stage to run a simple shell command simulating tests

Configure the pipeline to trigger on code changes

Print a message showing the test result

💡 Why This Matters

🌍 Real World

Continuous Integration helps teams catch bugs early by automatically testing code changes. Jenkins is a popular tool to automate this process.

💼 Career

Understanding CI pipelines is essential for DevOps roles and software developers to ensure code quality and faster delivery.

1

Create a basic Jenkins pipeline

Create a Jenkins pipeline script with a pipeline block and an empty stages section.

Jenkins

pipeline {
    agent any
    stages {
        // Your code here
    }
}

Hint

Start by writing the pipeline block with agent any and an empty stages block.

2

Add a test stage to the pipeline

Inside the stages block, add a stage named Test that runs a shell command echo Running tests.

Jenkins

pipeline {
    agent any
    stages {
        // Add a stage named 'Test' that runs 'echo Running tests'
    }
}

Hint

Use stage('Test') with steps and inside it run sh 'echo Running tests'.

3

Configure the pipeline to trigger on code changes

Add a triggers block inside the pipeline that uses pollSCM('* * * * *') to check for code changes every minute.

Jenkins

pipeline {
    agent any
    triggers {
        // Add pollSCM trigger here
    }
    stages {
        stage('Test') {
            steps {
                sh 'echo Running tests'
            }
        }
    }
}

Hint

Inside pipeline, add triggers { pollSCM('* * * * *') } to poll for changes every minute.

4

Print a message showing the test result

Add a post block inside the pipeline that prints echo 'Tests completed successfully' when the pipeline succeeds.

Jenkins

pipeline {
    agent any
    triggers {
        pollSCM('* * * * *')
    }
    stages {
        stage('Test') {
            steps {
                sh 'echo Running tests'
            }
        }
    }
    // Add a post block to print a success message
}

Hint

Use post { success { echo 'Tests completed successfully' } } inside the pipeline to print after success.

Practice

1. What is the main goal of Continuous Integration (CI) in software development?

easy

A. To write code without any collaboration

B. To deploy code directly to production without testing

C. To merge code changes frequently and test them automatically

D. To manually test code after all features are complete

Solution

1. Step 1: Understand the purpose of Continuous Integration

   Continuous Integration means developers merge their code changes often to avoid conflicts and detect errors early.

2. Step 2: Identify the key activity in CI

   Automatic testing after merging helps catch problems quickly and keeps the codebase healthy.

3. Final Answer:

   To merge code changes frequently and test them automatically -> Option C

4. Quick Check:

   CI = Frequent merge + automatic test [OK]

Hint: CI means frequent merges with automatic tests [OK]

Common Mistakes:

• Thinking CI means skipping tests
• Believing CI is only about deployment
• Assuming CI means no collaboration

2. Which Jenkins feature is commonly used to implement Continuous Integration pipelines?

easy

A. Jenkins Executor

B. Jenkins Agent

C. Jenkins Node

D. Jenkinsfile

Solution

1. Step 1: Identify Jenkins components related to pipelines

   Jenkinsfile is a text file that defines the steps of a CI pipeline in code form.

2. Step 2: Understand the role of Jenkinsfile in CI

   It allows automation of build, test, and deploy steps, making CI repeatable and consistent.

3. Final Answer:

   Jenkinsfile -> Option D

4. Quick Check:

   Pipeline code = Jenkinsfile [OK]

Hint: Pipeline code lives in Jenkinsfile [OK]

Common Mistakes:

• Confusing Jenkinsfile with Jenkins Agent
• Thinking Jenkins Node defines pipeline steps
• Mixing Jenkins Executor with pipeline definition

3. Given this Jenkins pipeline snippet:

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

What will Jenkins output during the 'Test' stage?

medium

A. Testing...

B. Building...

C. Build and Test

D. No output

Solution

1. Step 1: Read the pipeline stages and steps

   The 'Test' stage contains a step that echoes 'Testing...'.

2. Step 2: Understand Jenkins output behavior

   During the 'Test' stage, Jenkins runs the echo command and outputs 'Testing...'.

3. Final Answer:

   Testing... -> Option A

4. Quick Check:

   Test stage echo = 'Testing...' [OK]

Hint: Echo inside stage prints that stage's message [OK]

Common Mistakes:

• Confusing output of Build stage with Test stage
• Expecting combined output in one stage
• Thinking no output appears without explicit print

4. You wrote this Jenkins pipeline snippet:

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

What is the error and how to fix it?

medium

A. Missing agent declaration; add 'agent any'

B. Typo in 'ech' command; change to 'echo'

C. Stages block is missing; add 'stages' keyword

D. No error; pipeline is correct

Solution

1. Step 1: Identify the incorrect command in the Test stage

   The command 'ech' is not valid; it should be 'echo' to print text.

2. Step 2: Correct the typo to fix the pipeline

   Changing 'ech' to 'echo' will allow Jenkins to run the Test stage without errors.

3. Final Answer:

   Typo in 'ech' command; change to 'echo' -> Option B

4. Quick Check:

   Command typo fixed by 'echo' [OK]

Hint: Check spelling of commands carefully [OK]

Common Mistakes:

• Ignoring typo and expecting pipeline to run
• Adding unnecessary agent block
• Misunderstanding stages block presence

5. You want to set up a Jenkins pipeline that automatically builds and tests your code every time a developer pushes changes. Which two steps are essential to implement Continuous Integration correctly?

hard

A. Write a Jenkinsfile defining build and test stages; configure Jenkins to trigger on code push

B. Manually run builds after code is merged; deploy to production immediately

C. Write a Jenkinsfile with only deployment steps; ignore tests

D. Use Jenkins only for deployment; test code locally

Solution

1. Step 1: Define automated build and test in Jenkinsfile

   Continuous Integration requires automated steps to build and test code on every change.

2. Step 2: Configure Jenkins to trigger pipeline on code push

   Automatic triggering ensures CI runs without manual intervention, catching issues early.

3. Final Answer:

   Write a Jenkinsfile defining build and test stages; configure Jenkins to trigger on code push -> Option A

4. Quick Check:

   CI needs automation + trigger on push [OK]

Hint: Automate build/test and trigger on push [OK]

Common Mistakes:

• Skipping tests in pipeline
• Running builds manually
• Using Jenkins only for deployment