Agent directive in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline snippet?

Consider this Jenkins declarative pipeline snippet using the agent directive:

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        echo 'Running on any available agent'
      }
    }
  }
}

What will Jenkins do when this pipeline runs?

Jenkins

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        echo 'Running on any available agent'
      }
    }
  }
}

A Jenkins will run the pipeline on any available agent node and print 'Running on any available agent'.

B Jenkins will run the pipeline only on the master node and print 'Running on any available agent'.

C Jenkins will fail to run because 'agent any' is invalid syntax.

D Jenkins will run the pipeline on a docker container by default.

💡 Hint

Think about what agent any means in Jenkins pipelines.

The agent any directive tells Jenkins to run the pipeline on any available agent node. It does not restrict to master or docker unless specified.

🧠 Conceptual

intermediate

Which agent directive syntax specifies running on a specific label?

In Jenkins declarative pipelines, how do you specify that the pipeline should run only on agents with a specific label?

A agent none

B agent any

C agent { label 'my-label' }

D agent { docker 'my-label' }

💡 Hint

Labels help Jenkins pick specific nodes.

The syntax agent { label 'my-label' } tells Jenkins to run the pipeline on an agent node that has the label 'my-label'.

❓ Troubleshoot

advanced

Why does this pipeline fail to run on any agent?

Given this Jenkins pipeline snippet:

pipeline {
  agent none
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

Why does Jenkins fail to run this pipeline?

Jenkins

pipeline {
  agent none
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

A Because <code>agent none</code> disables automatic agent allocation and no agent is specified at stage level.

B Because <code>agent none</code> is invalid syntax and causes a syntax error.

C Because Jenkins requires <code>agent any</code> at the pipeline level always.

D Because the <code>echo</code> step is not allowed without a docker agent.

💡 Hint

Think about what agent none means and where agents can be specified.

agent none disables automatic agent allocation for the whole pipeline. If no agent is specified at the stage level, Jenkins has no node to run the steps on, causing failure.

🔀 Workflow

advanced

How to run different stages on different agents in one pipeline?

You want to run the 'Build' stage on an agent labeled 'linux' and the 'Test' stage on an agent labeled 'windows'. Which pipeline snippet achieves this?

A

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

B

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

C

pipeline {
  agent none
  stages {
    stage('Build') {
      steps { echo 'Building on Linux' }
    }
    stage('Test') {
      steps { echo 'Testing on Windows' }
    }
  }
}

D

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

💡 Hint

Remember that agent none disables global agent and you can specify agents per stage.

Setting agent none at pipeline level disables automatic agent allocation. Then each stage can specify its own agent { label '...' } to run on different nodes.

✅ Best Practice

expert

What is the best practice for using the agent directive in multi-stage pipelines?

In a Jenkins declarative pipeline with multiple stages requiring different environments, what is the best practice for using the agent directive?

A Use <code>agent any</code> at the pipeline level and avoid specifying agents at stage level to keep it simple.

B Use <code>agent none</code> at the pipeline level and specify <code>agent</code> per stage to optimize resource usage.

C Use <code>agent none</code> everywhere and run all steps on the master node manually.

D Use <code>agent docker</code> globally to run all stages inside the same container.

💡 Hint

Think about flexibility and resource optimization in pipelines.

Using agent none at the pipeline level disables automatic agent allocation, allowing each stage to specify its own agent. This is best for pipelines with stages needing different environments, optimizing resource use.