Node and stage blocks in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Jenkins Pipeline with nested node blocks

What will be the output of this Jenkins pipeline snippet when executed?

Jenkins

pipeline {
  agent none
  stages {
    stage('Build') {
      steps {
        script {
          node('linux') {
            echo 'Inside first node'
            node('windows') {
              echo 'Inside nested node'
            }
          }
        }
      }
    }
  }
}

A Syntax error due to nested node blocks

B Inside first node\nInside nested node

C Inside nested node\nInside first node

D Only 'Inside first node' is printed

💡 Hint

Think about how nested node blocks execute in Jenkins pipelines.

In Jenkins declarative pipelines, 'node' blocks are not allowed inside 'steps' blocks, whether single or nested. This is scripted DSL syntax and will cause a 'No such DSL method node' error.

🧠 Conceptual

intermediate

Purpose of 'agent none' in Jenkins pipeline

What is the main purpose of using agent none at the top level of a Jenkins declarative pipeline?

A To disable automatic agent allocation so stages can specify their own agents

B To force the pipeline to run on the master node only

C To automatically allocate an agent for all stages

D To skip all stages in the pipeline

💡 Hint

Consider how agent allocation works when you want different stages on different nodes.

Using 'agent none' disables automatic agent allocation at the pipeline level, allowing each stage to specify its own node or agent block.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline fail with 'No such DSL method node' error?

Given this pipeline snippet, why does Jenkins report 'No such DSL method node' error?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        node('linux') {
          echo 'Running tests'
        }
      }
    }
  }
}

A Because 'node' requires a label but 'linux' is undefined

B Because the 'agent any' conflicts with the 'node' block

C Because 'node' block is not allowed inside 'steps' in declarative pipelines

D Because 'echo' is not allowed inside 'node' blocks

💡 Hint

Check the allowed syntax inside declarative pipeline 'steps' blocks.

In declarative pipelines, 'node' blocks are not allowed inside 'steps'. Instead, use 'agent' at stage level or script blocks for scripted syntax.

🔀 Workflow

advanced

Correct stage and node usage for parallel builds

You want to run two builds in parallel on different nodes: one on 'linux' and one on 'windows'. Which pipeline snippet correctly achieves this?

Jenkins

pipeline {
  agent none
  stages {
    stage('Parallel Builds') {
      parallel {
        'Linux Build': {
          node('linux') {
            echo 'Building on Linux'
          }
        },
        'Windows Build': {
          node('windows') {
            echo 'Building on Windows'
          }
        }
      }
    }
  }
}

A The pipeline runs sequentially because 'parallel' is not allowed inside 'stages'.

B The pipeline runs only on the master node ignoring labels.

C The pipeline will fail because 'agent' cannot be used inside parallel stages.

D The given pipeline snippet runs both builds in parallel on specified nodes.

💡 Hint

Think about how parallel stages and agents work in declarative pipelines.

Declarative pipelines support parallel stages, but 'agent' cannot be used inside parallel branches/stages. Branches share the parent stage's agent. Use scripted 'node' {} inside parallel closures for different agents.

✅ Best Practice

expert

Best practice for using node blocks in Jenkins scripted pipeline

In a scripted Jenkins pipeline, what is the best practice for using node blocks to optimize resource usage and avoid unnecessary workspace allocation?

A Use multiple <code>node</code> blocks for each step to ensure clean workspace every time

B Use a single <code>node</code> block wrapping all build steps to minimize workspace allocation overhead

C Avoid <code>node</code> blocks entirely and run all steps on the master node

D Use nested <code>node</code> blocks with different labels inside each other for flexibility

💡 Hint

Consider workspace allocation and agent usage costs.

Using a single node block reduces overhead by allocating workspace once and reusing it, improving efficiency and reducing resource consumption.