Node and stage blocks in Jenkins - Mini Project: Build & Apply

Jenkins Pipeline with Node and Stage Blocks

📖 Scenario: You are setting up a Jenkins pipeline to automate a simple build process. Jenkins uses node blocks to allocate an executor and workspace, and stage blocks to organize the pipeline into steps.This project will guide you to create a Jenkins pipeline script with one node block and two stage blocks: one for building and one for testing.

🎯 Goal: Build a Jenkins pipeline script that uses a node block to allocate the workspace and contains two stage blocks named Build and Test. Each stage should echo a message indicating the current stage.

📋 What You'll Learn

Create a node block in the Jenkins pipeline script

Inside the node block, create two stage blocks named Build and Test

Inside each stage, use echo to print a message indicating the stage name

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software build, test, and deployment processes in real projects.

💼 Career

Understanding <code>node</code> and <code>stage</code> blocks is essential for DevOps engineers and automation specialists working with Jenkins.

1

Create a node block

Write a Jenkins pipeline script that starts with a node block. Inside the node block, add a comment // Pipeline steps will go here.

Jenkins

node {
    // Pipeline steps will go here
    // Your code here
}

Hint

The node block allocates an executor and workspace for your pipeline.

2

Add a stage block named Build

Inside the existing node block, add a stage block with the name Build. Inside this stage, add an echo statement that prints "Building the project...".

Jenkins

node {
    stage('Build') {
        // Your code here
    }
}

Hint

The stage block groups steps and the echo command prints messages in the Jenkins console.

3

Add a stage block named Test

Still inside the node block, after the Build stage, add another stage block named Test. Inside this stage, add an echo statement that prints "Running tests...".

Jenkins

node {
    stage('Build') {
        echo "Building the project..."
    }
    stage('Test') {
        // Your code here
    }
}

Hint

Add the Test stage after the Build stage inside the node block.

4

Print the pipeline completion message

After the Test stage, still inside the node block, add an echo statement that prints "Pipeline completed successfully.".

Jenkins

node {
    stage('Build') {
        echo "Building the project..."
    }
    stage('Test') {
        echo "Running tests..."
    }
    // Your code here
}

Hint

The final echo prints a message after all stages finish.

Practice

1. What is the main purpose of a node block in a Jenkins pipeline?

easy

A. To declare environment variables for the pipeline

B. To define a named step grouping in the pipeline

C. To specify the machine or agent where the pipeline steps run

D. To send notifications after the pipeline finishes

Solution

1. Step 1: Understand the role of node block

   The node block tells Jenkins which machine or agent will run the enclosed commands.

2. Step 2: Differentiate from stage block

   The stage block is for grouping steps with a name, not for selecting the machine.

3. Final Answer:

   To specify the machine or agent where the pipeline steps run -> Option C

4. Quick Check:

   Node block = machine selection [OK]

Hint: Node block = where commands run, stage block = what step runs [OK]

Common Mistakes:

• Confusing node with stage blocks
• Thinking node defines step names
• Assuming node sets environment variables

2. Which of the following is the correct syntax to define a stage inside a Jenkins pipeline?

easy

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

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

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

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

Solution

1. Step 1: Recall correct stage syntax

   The correct syntax uses stage('name') { steps { ... } } to define a stage with steps inside.

2. Step 2: Check each option

   stage('Build') { steps { echo 'Building...' } } matches the correct syntax. Options A, B, and D misuse keywords or structure.

3. Final Answer:

   stage('Build') { steps { echo 'Building...' } } -> Option D

4. Quick Check:

   Stage syntax = stage('name') { steps { ... } } [OK]

Hint: Stage blocks use stage('name') with steps inside [OK]

Common Mistakes:

• Using node instead of stage for grouping steps
• Missing steps block inside stage
• Incorrect colon or braces placement

3. Given the Jenkins pipeline snippet below, what will be the output?

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        node('linux') {
          echo 'Running on Linux node'
        }
      }
    }
  }
}

medium

A. Running on Linux node

B. Syntax error due to nested node inside steps

C. Pipeline runs but no output is shown

D. Error: agent and node blocks cannot be combined

Solution

1. Step 1: Analyze pipeline structure

   The pipeline uses agent any globally and inside the stage steps calls node('linux') to run commands on a Linux node.

2. Step 2: Understand nested node usage

   Nested node blocks inside steps are allowed in scripted pipelines; here it will run the echo command on the specified node.

3. Final Answer:

   Running on Linux node -> Option A

4. Quick Check:

   Nested node runs commands on specified agent [OK]

Hint: Nested node inside steps runs commands on chosen agent [OK]

Common Mistakes:

• Assuming nested node causes syntax error
• Thinking agent any forbids node blocks
• Expecting no output from echo

4. Identify the error in this Jenkins pipeline snippet:

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

medium

A. The node block is incorrectly placed inside stage

B. Missing agent inside the stage block

C. The steps block should be outside node

D. The echo command is invalid inside steps

Solution

1. Step 1: Review pipeline block structure

   Declarative pipelines require agent to specify where stages run; node is not valid inside stage in declarative syntax.

2. Step 2: Identify correct usage

   Instead of node, the stage should have an agent block or rely on global agent any.

3. Final Answer:

   The node block is incorrectly placed inside stage -> Option A

4. Quick Check:

   Declarative stage needs agent, not node [OK]

Hint: Use agent, not node, inside declarative stage blocks [OK]

Common Mistakes:

• Using node block inside declarative stage
• Confusing steps placement
• Thinking echo is invalid inside steps

5. You want to run two stages in your Jenkins pipeline: 'Build' on a Linux node and 'Test' on a Windows node. Which pipeline snippet correctly uses node and stage blocks to achieve this?

hard

A. pipeline {
agent none
stages {
stage('Build') {
steps {
node('linux') {
echo 'Building on Linux'
}
}
}
stage('Test') {
steps {
node('windows') {
echo 'Testing on Windows'
}
}
}
}
}

B. pipeline {
agent any
stages {
stage('Build') {
agent { label 'linux' }
steps {
echo 'Building on Linux'
}
}
stage('Test') {
agent { label 'windows' }
steps {
echo 'Testing on Windows'
}
}
}
}

C. pipeline {
agent any
stages {
stage('Build') {
node('linux') {
steps {
echo 'Building on Linux'
}
}
}
stage('Test') {
node('windows') {
steps {
echo 'Testing on Windows'
}
}
}
}
}

D. pipeline {
agent none
stages {
stage('Build') {
agent { label 'windows' }
steps {
echo 'Building on Linux'
}
}
stage('Test') {
agent { label 'linux' }
steps {
echo 'Testing on Windows'
}
}
}
}

Solution

1. Step 1: Understand declarative pipeline agent usage

   In declarative pipelines, use agent { label 'name' } inside stages to specify the node label.

2. Step 2: Evaluate each option

   pipeline { agent any stages { stage('Build') { agent { label 'linux' } steps { echo 'Building on Linux' } } stage('Test') { agent { label 'windows' } steps { echo 'Testing on Windows' } } } } correctly uses agent inside each stage with labels 'linux' and 'windows'. pipeline { agent none stages { stage('Build') { steps { node('linux') { echo 'Building on Linux' } } } stage('Test') { steps { node('windows') { echo 'Testing on Windows' } } } } } misuses node inside steps in declarative style. pipeline { agent any stages { stage('Build') { node('linux') { steps { echo 'Building on Linux' } } } stage('Test') { node('windows') { steps { echo 'Testing on Windows' } } } } } uses node blocks incorrectly inside stage. pipeline { agent none stages { stage('Build') { agent { label 'windows' } steps { echo 'Building on Linux' } } stage('Test') { agent { label 'linux' } steps { echo 'Testing on Windows' } } } } swaps labels incorrectly.

3. Final Answer:

   Option B uses agent labels correctly inside stages -> Option B

4. Quick Check:

   Use agent { label } inside stages for node selection [OK]

Hint: Use agent { label 'name' } inside stages, not node blocks [OK]

Common Mistakes:

• Using node blocks inside declarative stages
• Swapping node labels by mistake
• Not setting agent none when using stage agents