Labels for agent selection in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Agent selection with label in Jenkins pipeline

What will be the output or behavior when running this Jenkins pipeline snippet?

Jenkins

pipeline {
  agent { label 'linux && docker' }
  stages {
    stage('Build') {
      steps {
        echo "Running on agent with linux and docker labels"
      }
    }
  }
}

A The pipeline runs on any agent that has either 'linux' or 'docker' label assigned.

B The pipeline fails to start due to invalid label syntax.

C The pipeline runs only on agents that have both 'linux' and 'docker' labels assigned.

D The pipeline runs on the first available agent regardless of labels.

💡 Hint

Think about how Jenkins interprets label expressions with && operator.

Using 'label "linux && docker"' means the agent must have both labels 'linux' and 'docker' to run the pipeline. It is a logical AND condition.

🧠 Conceptual

intermediate

Understanding label expressions for agent selection

Which label expression correctly selects agents that have the label 'windows' but not the label 'test'?

A windows && !test

B windows || !test

C !windows && test

D !windows || test

💡 Hint

Use logical AND and NOT operators to combine labels.

The expression 'windows && !test' means select agents that have 'windows' label and do not have 'test' label.

❓ Troubleshoot

advanced

Troubleshooting agent label mismatch in Jenkins

A Jenkins pipeline with agent label 'docker && gpu' fails to find a suitable agent. Which is the most likely cause?

A The Jenkins master node is offline.

B The label expression syntax is incorrect and causes a parsing error.

C The pipeline requires a Windows agent but labels specify Linux agents.

D No agent has both 'docker' and 'gpu' labels assigned.

💡 Hint

Check the labels assigned to your agents carefully.

If no agent has both 'docker' and 'gpu' labels, Jenkins cannot find a matching agent to run the pipeline.

🔀 Workflow

advanced

Configuring Jenkins pipeline to run on multiple label options

You want a Jenkins pipeline to run on agents that have either 'mac' or 'linux' label. Which agent label expression should you use?

A mac && linux

B mac || linux

C mac, linux

D mac linux

💡 Hint

Use logical OR operator to select agents with either label.

The expression 'mac || linux' means the pipeline can run on agents with 'mac' label or 'linux' label.

✅ Best Practice

expert

Best practice for labeling Jenkins agents for flexible selection

Which approach is best to label Jenkins agents to allow pipelines to select agents flexibly by OS and capability?

A Assign multiple specific labels like 'linux', 'docker', 'gpu' to each agent based on capabilities.

B Assign a single generic label like 'build-agent' to all agents regardless of capabilities.

C Use only OS labels like 'windows' or 'linux' and ignore capabilities.

D Do not use labels; rely on agent names for selection.

💡 Hint

Think about how pipelines can select agents based on multiple criteria.

Assigning multiple specific labels allows pipelines to select agents flexibly by combining labels for OS and capabilities.