Steps within stages in Jenkins - Mini Project: Build & Apply

Jenkins Pipeline: Steps within Stages

📖 Scenario: You are setting up a Jenkins pipeline to automate a simple build process. The pipeline has stages, and each stage contains steps that perform specific tasks.Think of stages as chapters in a book, and steps as the sentences that tell the story in each chapter.

🎯 Goal: Build a Jenkins pipeline script with one stage named Build that contains two steps: one to print a message and another to run a shell command.

📋 What You'll Learn

Create a Jenkins pipeline with a pipeline block

Add a stage named Build

Inside the Build stage, add two steps: one echo and one sh

The echo step must print exactly Starting build...

The sh step must run the command echo Build complete

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software builds and tests, making development faster and less error-prone.

💼 Career

Understanding pipeline stages and steps is essential for DevOps engineers to create reliable CI/CD workflows.

1

Create the pipeline and stage

Write a Jenkins pipeline script that starts with a pipeline block and contains one stage named Build. Use the agent any directive inside the pipeline.

Jenkins

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

Hint

Start with pipeline {}, add agent any, then add stages {} with one stage('Build') {} inside.

2

Add the echo step inside the Build stage

Inside the steps block of the Build stage, add an echo step that prints exactly Starting build....

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Add echo step here
            }
        }
    }
}

Hint

Use echo 'Starting build...' inside the steps block.

3

Add the shell command step inside the Build stage

Add a sh step inside the steps block of the Build stage that runs the shell command echo Build complete.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Starting build...'
                // Add sh step here
            }
        }
    }
}

Hint

Use sh 'echo Build complete' to run the shell command inside steps.

4

Print the pipeline script

Print the entire Jenkins pipeline script you wrote so far.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Starting build...'
                sh 'echo Build complete'
            }
        }
    }
}

// Print the pipeline script below
// Your code here

Hint

In Jenkins, the pipeline script is saved as a Jenkinsfile. Here, just ensure your final script matches the previous steps.

Practice

1. What is the main purpose of steps inside a Jenkins stage?

easy

A. To define the actual commands or actions Jenkins will execute

B. To name the stage in the pipeline

C. To set environment variables for the pipeline

D. To configure Jenkins plugins

Solution

1. Step 1: Understand the role of stages

   Stages organize the pipeline into sections but do not run commands themselves.

2. Step 2: Identify what steps do inside stages

   Steps contain the actual commands or scripts Jenkins executes during that stage.

3. Final Answer:

   To define the actual commands or actions Jenkins will execute -> Option A

4. Quick Check:

   Steps = commands inside stages [OK]

Hint: Steps run commands; stages just group them [OK]

Common Mistakes:

• Confusing stage name with steps
• Thinking steps configure plugins
• Believing steps set environment variables

2. Which of the following is the correct syntax to define a step that prints 'Hello World' inside a Jenkins declarative pipeline stage?

easy

A. script { print 'Hello World' }

B. steps { echo 'Hello World' }

C. steps: echo('Hello World')

D. stage { echo 'Hello World' }

Solution

1. Step 1: Recall declarative pipeline syntax for steps

   Inside a stage, steps are defined with the steps { ... } block.

2. Step 2: Check the correct command to print

   The echo command prints messages in Jenkins pipelines.

3. Final Answer:

   steps { echo 'Hello World' } -> Option B

4. Quick Check:

   steps block + echo command = correct syntax [OK]

Hint: Use steps { echo 'text' } to print in Jenkins [OK]

Common Mistakes:

• Using stage instead of steps for commands
• Wrong colon syntax in steps
• Using print instead of echo

3. Given this Jenkins pipeline snippet, what will be the output in the console?

stage('Build') {
  steps {
    echo 'Starting build'
    sh 'echo Build complete'
  }
}

medium

A. Syntax error in pipeline

B. Build complete\nStarting build

C. Starting build only

D. Starting build\nBuild complete

Solution

1. Step 1: Understand the order of steps execution

   Steps run sequentially: first echo 'Starting build', then shell command sh 'echo Build complete'.

2. Step 2: Determine console output

   The first prints 'Starting build', the shell prints 'Build complete', so output is both lines in order.

3. Final Answer:

   Starting build\nBuild complete -> Option D

4. Quick Check:

   Steps run in order, echo then shell output [OK]

Hint: Steps run top to bottom, echo then shell output [OK]

Common Mistakes:

• Assuming shell output appears before echo
• Thinking only echo prints
• Confusing syntax causing errors

4. Identify the error in this Jenkins pipeline stage and how to fix it:

stage('Test') {
  steps
    echo 'Running tests'
}

medium

A. stage keyword should be inside steps

B. echo command is invalid; use print instead

C. Missing curly braces {} after steps; add steps { ... }

D. No error; pipeline is correct

Solution

1. Step 1: Check syntax for steps block

   The steps block must have curly braces enclosing commands: steps { ... }.

2. Step 2: Identify missing braces causing syntax error

   Here, steps is followed directly by echo without braces, which is invalid.

3. Final Answer:

   Missing curly braces {} after steps; add steps { ... } -> Option C

4. Quick Check:

   steps block requires braces { } [OK]

Hint: Always wrap steps commands inside steps { } [OK]

Common Mistakes:

• Omitting braces after steps
• Using print instead of echo
• Placing stage inside steps

5. You want to run multiple shell commands sequentially inside a Jenkins stage. Which is the best way to organize these steps?

hard

A. Use a single sh step with commands separated by semicolons inside steps { }

B. Write multiple stage blocks, each with one sh command

C. Put all commands inside environment block

D. Use multiple steps blocks inside one stage

Solution

1. Step 1: Understand how to run multiple shell commands

   Multiple commands can be run in one sh step by separating them with semicolons.

2. Step 2: Identify correct pipeline structure

   Only one steps block is allowed per stage; multiple commands go inside one sh step or multiple steps inside the block.

3. Final Answer:

   Use a single sh step with commands separated by semicolons inside steps { } -> Option A

4. Quick Check:

   One steps block + one sh with multiple commands [OK]

Hint: Combine shell commands with semicolons inside one sh step [OK]

Common Mistakes:

• Using multiple stages for commands
• Trying multiple steps blocks inside one stage
• Putting commands in environment block