Jenkins in the CI/CD ecosystem - Mini Project: Build & Apply

Jenkins in the CI/CD ecosystem

📖 Scenario: You are working as a DevOps engineer in a small software team. Your team wants to automate the process of building and testing their code whenever a developer makes changes. You will use Jenkins, a popular automation tool, to create a simple pipeline that runs a build and test job automatically.

🎯 Goal: Build a basic Jenkins pipeline script that defines a job with stages for building and testing code. This pipeline will help your team automate their software delivery process.

📋 What You'll Learn

Create a Jenkins pipeline script with a pipeline block

Define an agent to run the pipeline

Add two stages: Build and Test

In the Build stage, run a shell command to print 'Building the project...'

In the Test stage, run a shell command to print 'Running tests...'

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software builds, tests, and deployments, saving time and reducing errors.

💼 Career

Understanding Jenkins pipelines is essential for DevOps roles to implement continuous integration and continuous delivery.

1

Create the basic Jenkins pipeline structure

Write a Jenkins pipeline script starting with pipeline {} and inside it, add an agent any block to specify that the pipeline can run on any available agent.

Jenkins

pipeline {
    agent any
    // Your code here
}

Hint

Start with pipeline {} and add agent any inside it.

2

Add the Build stage

Inside the pipeline block, add a stages block. Then add a stage named Build that runs a shell command echo 'Building the project...' inside a steps block.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Hint

Use stages {} to group stages, then add stage('Build') { steps { sh "echo 'Building the project...'" } }.

3

Add the Test stage

Inside the existing stages block, add another stage named Test. In this stage, add a steps block that runs the shell command echo 'Running tests...'.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh "echo 'Building the project...'"
            }
        }
        // Your code here
    }
}

Hint

Add stage('Test') { steps { sh "echo 'Running tests...'" } } inside stages.

4

Print the pipeline script

Print the entire Jenkins pipeline script to verify it is correct. Use println to output the pipeline script as a string.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh "echo 'Building the project...'"
            }
        }
        stage('Test') {
            steps {
                sh "echo 'Running tests...'"
            }
        }
    }
}

// Your code here

Hint

Use println with the full pipeline script as a string, including newlines and indentation.

Practice

1. What is the primary role of Jenkins in the CI/CD ecosystem?

easy

A. Automate building, testing, and deploying software

B. Write application code

C. Design user interfaces

D. Manage database schemas

Solution

1. Step 1: Understand Jenkins purpose

   Jenkins is a tool designed to automate software processes like building, testing, and deployment.

2. Step 2: Compare options with Jenkins role

   Only Automate building, testing, and deploying software matches Jenkins' automation role in CI/CD; others relate to unrelated tasks.

3. Final Answer:

   Automate building, testing, and deploying software -> Option A

4. Quick Check:

   Jenkins automates CI/CD tasks = A [OK]

Hint: Jenkins automates software delivery steps [OK]

Common Mistakes:

• Confusing Jenkins with coding or UI design tools
• Thinking Jenkins manages databases
• Assuming Jenkins writes application code

2. Which of the following is the correct syntax to define a simple Jenkins pipeline in a Jenkinsfile?

easy

A. job {
steps {
echo 'Building...'
}
}

B. build {
steps {
echo 'Building...'
}
}

C. pipeline: {
stage('Build') {
echo 'Building...'
}
}

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

Solution

1. Step 1: Review Jenkins pipeline syntax

   The correct Jenkins pipeline uses the 'pipeline' block with 'agent' and 'stages' sections.

2. Step 2: Match syntax with options

   pipeline { agent any stages { stage('Build') { steps { echo 'Building...' } } } } correctly shows the pipeline structure with agent, stages, and steps. Others have invalid or incomplete syntax.

3. Final Answer:

   Correct Jenkins pipeline syntax with agent and stages -> Option D

4. Quick Check:

   Valid Jenkinsfile uses 'pipeline' block = D [OK]

Hint: Look for 'pipeline', 'agent', and 'stages' keywords [OK]

Common Mistakes:

• Missing 'agent' block in pipeline
• Using 'build' or 'job' instead of 'pipeline'
• Incorrect block nesting or missing braces

3. Given this Jenkins pipeline snippet, what will be the output when the pipeline runs?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        echo 'Starting tests'
        script {
          def result = 2 + 3
          echo "Result is ${result}"
        }
      }
    }
  }
}

medium

A. Starting tests
Result is ${result}

B. Starting tests
Result is 5

C. Starting tests
Result is 23

D. Syntax error in pipeline

Solution

1. Step 1: Understand pipeline script block execution

   The 'script' block allows Groovy code execution; 'def result = 2 + 3' calculates 5.

2. Step 2: Analyze echo statements

   First echo prints 'Starting tests', second prints 'Result is 5' using string interpolation.

3. Final Answer:

   Starting tests Result is 5 -> Option B

4. Quick Check:

   Groovy evaluates expressions inside ${} = C [OK]

Hint: Groovy evaluates ${} inside double quotes [OK]

Common Mistakes:

• Treating ${result} as plain text
• Concatenating numbers as strings
• Assuming syntax error due to script block

4. You have this Jenkins pipeline snippet:

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

What is the problem with this pipeline?

medium

A. Multiple 'stages' blocks are not allowed in one pipeline

B. Missing 'agent' declaration

C. Echo commands are invalid in Jenkinsfile

D. Pipeline must have at least three stages

Solution

1. Step 1: Review pipeline structure rules

   A Jenkins pipeline can have only one 'stages' block containing multiple 'stage' blocks.

2. Step 2: Identify error in given pipeline

   Here, there are two separate 'stages' blocks, which is invalid syntax.

3. Final Answer:

   Multiple 'stages' blocks are not allowed in one pipeline -> Option A

4. Quick Check:

   Only one 'stages' block per pipeline = B [OK]

Hint: Only one 'stages' block allowed in Jenkinsfile [OK]

Common Mistakes:

• Thinking multiple 'stages' blocks are valid
• Confusing missing agent with stages error
• Assuming echo commands cause errors

5. You want to create a Jenkins pipeline that builds your project only if the branch is 'main' and runs tests on all branches. Which pipeline snippet correctly implements this logic?

pipeline {
  agent any
  stages {
    stage('Build') {
      when {
        branch 'main'
      }
      steps {
        echo 'Building main branch'
      }
    }
    stage('Test') {
      steps {
        echo 'Running tests'
      }
    }
  }
}

hard

A. The pipeline builds and tests only on 'main' branch

B. The pipeline builds on all branches and tests only on 'main'

C. The pipeline builds only on 'main' branch and tests on all branches as required

D. The pipeline builds and tests on all branches without conditions

Solution

1. Step 1: Understand 'when' condition in Build stage

   The 'when { branch 'main' }' condition restricts the Build stage to run only on the 'main' branch.

2. Step 2: Analyze Test stage behavior

   The Test stage has no 'when' condition, so it runs on all branches.

3. Final Answer:

   The pipeline builds only on 'main' branch and tests on all branches as required -> Option C

4. Quick Check:

   'when' limits build; test runs always = A [OK]

Hint: Use 'when' to limit stages by branch [OK]

Common Mistakes:

• Assuming all stages run on all branches
• Misplacing 'when' condition on Test stage
• Confusing branch names or conditions