Node and stage blocks in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage named 'Build'.

Jenkins

stage('[1]') {
    steps {
        echo 'Building the project'
    }
}

Drag options to blanks, or click blank then click option'

ATest

BDeploy

CBuild

DClean

Attempts:

3 left

💡 Hint

Common Mistakes

Using a stage name that does not match the intended phase.

Forgetting to put the stage name in quotes.

The stage block defines a phase in the Jenkins pipeline. Here, the stage is named 'Build'.

2fill in blank

medium

Complete the code to specify the node label 'linux' for running the pipeline.

Jenkins

node('[1]') {
    stage('Test') {
        steps {
            echo 'Running tests'
        }
    }
}

Drag options to blanks, or click blank then click option'

Adocker

Blinux

Cmac

Dwindows

Attempts:

3 left

💡 Hint

Common Mistakes

Using a node label that does not exist on the Jenkins server.

Forgetting to put the node label in quotes.

The node block specifies the agent where the pipeline or stage runs. Here, it runs on a node labeled 'linux'.

3fill in blank

hard

Fix the error in the node block to correctly specify the agent.

Jenkins

node [1] {
    stage('Deploy') {
        steps {
            echo 'Deploying application'
        }
    }
}

Drag options to blanks, or click blank then click option'

A'docker'

Bdocker

C'docker-agent'

Ddocker-agent

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the node label.

Using an incorrect label name.

The node label must be a string inside quotes. Without quotes, Jenkins will throw a syntax error.

4fill in blank

hard

Fill both blanks to create a stage named 'Test' that runs on a node labeled 'windows'.

Jenkins

node([1]) {
    stage([2]) {
        steps {
            echo 'Running tests'
        }
    }
}

Drag options to blanks, or click blank then click option'

A'windows'

B'Test'

C'test'

D'linux'

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the node label or stage name.

Using incorrect case for the stage name.

The node block requires the node label as a quoted string. The stage block requires the stage name as a quoted string.

5fill in blank

hard

Fill all three blanks to create a pipeline that runs on a 'linux' node, has a stage named 'Build', and echoes 'Building project'.

Jenkins

node([1]) {
    stage([2]) {
        steps {
            echo [3]
        }
    }
}

Drag options to blanks, or click blank then click option'

A'linux'

B'Build'

C'Building project'

D'Deploy'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around strings.

Using wrong stage name or echo message.

The node block uses the 'linux' label. The stage is named 'Build'. The echo command prints 'Building project' inside quotes.

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