CI/CD tools landscape in Jenkins - Mini Project: Build & Apply

CI/CD Tools Landscape with Jenkins

📖 Scenario: You are working as a DevOps engineer in a small software company. Your team wants to understand the basic setup of a Jenkins pipeline to automate building and testing their code.

🎯 Goal: Build a simple Jenkins pipeline script that defines stages for building and testing code. This will help your team see how Jenkins automates tasks step-by-step.

📋 What You'll Learn

Create a Jenkins pipeline script with a pipeline block

Add an agent to specify where the pipeline runs

Define two stages: Build and Test

In each stage, add a simple echo command to show the stage name

Print the pipeline completion message at the end

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software building, testing, and deployment, 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 a pipeline block and add an agent any line inside it.

Jenkins

pipeline {
    agent any
    // Your code here
}

Hint

The pipeline block is the main container. agent any means the pipeline can run on any available machine.

2

Add the Build stage

Inside the pipeline block, add a stages block. Then add a stage named Build with a steps block that contains echo 'Building the project...'.

Jenkins

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

Hint

The stages block holds all the steps your pipeline will run. Each stage groups related steps.

3

Add the Test stage

Inside the existing stages block, add another stage named Test with a steps block that contains echo 'Running tests...'.

Jenkins

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

Hint

Stages run one after another. Add the Test stage after Build to simulate testing.

4

Print pipeline completion message

Add a final stage named Complete inside the stages block with a steps block that contains echo 'Pipeline finished successfully.'. Then run the pipeline to see all messages.

Jenkins

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

Hint

The final stage confirms the pipeline ran all steps. The output shows messages from all stages in order.

Practice

1. What is the main purpose of CI/CD tools like Jenkins in software development?

easy

A. To design user interfaces

B. To write code manually

C. To automate building, testing, and deploying software

D. To manage hardware resources

Solution

1. Step 1: Understand CI/CD tools role

   CI/CD tools automate repetitive tasks in software development like building, testing, and deploying.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks. Only To automate building, testing, and deploying software matches the automation purpose.

3. Final Answer:

   To automate building, testing, and deploying software -> Option C

4. Quick Check:

   CI/CD tools automate software delivery = A [OK]

Hint: CI/CD tools automate software delivery steps [OK]

Common Mistakes:

• Confusing CI/CD tools with coding or design tools
• Thinking CI/CD tools manage hardware
• Assuming CI/CD tools replace developers

2. Which of the following is the correct way to define a stage in a Jenkins pipeline?

easy

A. stage('Build') { steps { echo 'Building...' } }

B. step('Build') { echo 'Building...' }

C. stage: Build { echo 'Building...' }

D. buildStage { echo 'Building...' }

Solution

1. Step 1: Recall Jenkins pipeline syntax

   Jenkins uses stage('name') { steps { ... } } to define stages.

2. Step 2: Check options for correct syntax

   Only stage('Build') { steps { echo 'Building...' } } matches the correct syntax with stage and steps blocks.

3. Final Answer:

   <code>stage('Build') { steps { echo 'Building...' } }</code> -> Option A

4. Quick Check:

   Correct Jenkins stage syntax = C [OK]

Hint: Stages use stage('name') with steps block [OK]

Common Mistakes:

• Using 'step' instead of 'stage'
• Missing the steps block inside stage
• Incorrect block syntax with colons or missing braces

3. Given this Jenkins pipeline snippet, what will be printed during the 'Test' stage?

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

medium

A. Testing... Building...

B. Testing...

C. Building...

D. Building... Testing...

Solution

1. Step 1: Understand pipeline stage order

   The pipeline runs stages in order: 'Build' then 'Test'.

2. Step 2: Identify echo outputs

   'Build' stage prints 'Building...', 'Test' stage prints 'Testing...'. Both run sequentially.

3. Final Answer:

   Building... Testing... -> Option D

4. Quick Check:

   Stages run in order, print messages in sequence = B [OK]

Hint: Stages run sequentially, outputs print in order [OK]

Common Mistakes:

• Assuming stages run in parallel by default
• Mixing output order
• Ignoring all stages run unless skipped

4. Identify the error in this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Deploy') {
      step { echo 'Deploying...' }
    }
  }
}

medium

A. The keyword should be 'steps' not 'step'

B. Missing agent declaration

C. Stage name must be lowercase

D. Echo command is invalid

Solution

1. Step 1: Check pipeline syntax for stages

   Inside a stage, the correct block is steps (plural), not step.

2. Step 2: Verify other parts

   Agent is declared, stage name case is allowed, echo is valid. Only 'step' is wrong.

3. Final Answer:

   The keyword should be 'steps' not 'step' -> Option A

4. Quick Check:

   Use 'steps' block inside stage = A [OK]

Hint: Inside stage use 'steps' plural block [OK]

Common Mistakes:

• Using 'step' instead of 'steps'
• Thinking stage names must be lowercase
• Assuming echo is not allowed

5. You want to create a Jenkins pipeline that builds, tests, and deploys only if tests pass. Which approach best fits this CI/CD workflow?

hard

A. Skip Test stage and deploy immediately after Build

B. Define sequential stages: Build, Test, Deploy; Deploy runs only if Test succeeds

C. Deploy first, then Build and Test in any order

D. Run Build and Deploy stages in parallel, then Test last

Solution

1. Step 1: Understand CI/CD workflow logic

   Tests must pass before deploying to avoid broken releases.

2. Step 2: Choose pipeline structure

   Sequential stages Build -> Test -> Deploy ensure deploy runs only if tests succeed.

3. Step 3: Evaluate other options

   Parallel or skipping tests risks deploying broken code; deploying first is illogical.

4. Final Answer:

   Define sequential stages: Build, Test, Deploy; Deploy runs only if Test succeeds -> Option B

5. Quick Check:

   Sequential stages with test gate = D [OK]

Hint: Deploy only after successful tests in sequence [OK]

Common Mistakes:

• Running deploy before tests
• Skipping tests to save time
• Running build and deploy in parallel