Labels for agent selection in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of labels in Jenkins agent selection?

Labels help Jenkins identify and select the right agent (worker) to run a job based on the agent's capabilities or characteristics.

beginner

How do you assign a label to a Jenkins agent?

In Jenkins, go to the agent's configuration page and enter the label(s) in the 'Labels' field. Multiple labels can be separated by spaces.

intermediate

What happens if a Jenkins job specifies a label that no agent has?

The job will remain in the queue and wait until an agent with the specified label becomes available or the label is corrected.

intermediate

How do you specify a label for agent selection in a Jenkins Pipeline script?

Use the 'agent' directive with 'label' inside the pipeline block, for example:

pipeline { agent { label 'linux' } stages { ... } }

intermediate

Can a Jenkins agent have multiple labels? Why is this useful?

Yes, an agent can have multiple labels. This allows flexible job assignment because jobs can request any one of the labels that match the agent's capabilities.

What is the main use of labels in Jenkins agent selection?

A To configure Jenkins plugins

B To name the Jenkins job

C To set job build triggers

D To identify which agent should run a job

Labels help Jenkins pick the right agent to run a job based on matching labels.

Where do you assign labels to a Jenkins agent?

A In the Jenkins system logs

B In the Jenkins global settings

C In the agent's configuration page

D Inside the job's build steps

Labels are assigned on the agent's configuration page to describe its capabilities.

What happens if no agent matches the label specified in a Jenkins job?

A The job waits in the queue until an agent is available

B The job runs on the master node

C The job is canceled automatically

D The job runs on any available agent

The job waits in the queue until an agent with the matching label is free.

How do you specify an agent label in a Jenkins Pipeline script?

A agent { label 'labelName' }

B node('labelName') { }

C stage('labelName') { }

D build('labelName')

The 'agent' directive with 'label' specifies which agent label to use in a pipeline.

Why might an agent have multiple labels?

A To confuse Jenkins

B To allow jobs with different label requirements to run on it

C To increase build speed

D To reduce disk space usage

Multiple labels let an agent serve different types of jobs by matching various label requests.

Explain how Jenkins uses labels to select agents for running jobs.

Think about how Jenkins finds the right worker for a task.

Describe how to assign and use labels in a Jenkins Pipeline script.

Focus on both the agent setup and pipeline syntax.

Practice

1.

What is the main purpose of using labels in Jenkins agent selection?

easy

A. To store job build logs

B. To change the Jenkins user interface theme

C. To tell Jenkins which agent can run a specific job

D. To configure Jenkins system settings

Solution

1. Step 1: Understand Jenkins agent labels

   Labels are tags assigned to agents to identify their capabilities or roles.

2. Step 2: Purpose of labels in job assignment

   Jenkins uses these labels to select the right agent that matches the job requirements.

3. Final Answer:

   To tell Jenkins which agent can run a specific job -> Option C

4. Quick Check:

   Labels guide agent selection = A [OK]

Hint: Labels connect jobs to suitable agents quickly [OK]

Common Mistakes:

• Thinking labels change UI or store logs
• Confusing labels with system settings

2.

Which of the following is the correct syntax to select an agent with label linux and docker in Jenkins pipeline?

easy

A. agent { label linux docker }

B. agent { label 'linux, docker' }

C. agent { label 'linux || docker' }

D. agent { label 'linux && docker' }

Solution

1. Step 1: Understand label expressions in Jenkins

   Jenkins uses logical operators like && for AND and || for OR in label expressions.

2. Step 2: Correct syntax for AND condition

   To require both labels, use 'linux && docker' inside the label field.

3. Final Answer:

   agent { label 'linux && docker' } -> Option D

4. Quick Check:

   AND labels use && = D [OK]

Hint: Use && for AND, || for OR in label expressions [OK]

Common Mistakes:

• Using space-separated labels without operators
• Using commas instead of logical operators
• Confusing AND (&&) with OR (||)

3.

Given this Jenkins pipeline snippet, what agent will run the job if agents have labels linux, docker, and gpu?

agent { label 'linux && (docker || gpu)' }

medium

A. An agent with linux and either docker or gpu labels

B. An agent with linux and gpu labels

C. An agent with both linux and docker labels

D. Any agent with linux, docker, and gpu labels all together

Solution

1. Step 1: Analyze label expression

   The expression requires the agent to have the 'linux' label AND either 'docker' OR 'gpu' label.

2. Step 2: Determine matching agents

   Agents with 'linux' plus 'docker' or 'linux' plus 'gpu' satisfy the condition.

3. Final Answer:

   An agent with linux and either docker or gpu labels -> Option A

4. Quick Check:

   linux AND (docker OR gpu) = A [OK]

Hint: Parentheses group OR conditions, AND applies outside [OK]

Common Mistakes:

• Thinking all three labels are required
• Ignoring parentheses in label expressions
• Assuming OR means both labels must be present

4.

What is wrong with this Jenkins pipeline agent label expression that causes the job to wait indefinitely?

agent { label 'linux && docker || gpu' }

medium

A. Labels must be quoted with double quotes, not single quotes

B. Missing parentheses causing wrong operator precedence

C. Using commas instead of logical operators

D. Agent label cannot contain logical operators

Solution

1. Step 1: Understand operator precedence in label expressions

   Logical AND (&&) has higher precedence than OR (||), so expression is parsed as '(linux && docker) || gpu'.

2. Step 2: Identify why job waits

   If no agent has both linux and docker, but some have gpu alone, job may pick gpu agents. If gpu agents are missing or busy, job waits.

3. Final Answer:

   Missing parentheses causing wrong operator precedence -> Option B

4. Quick Check:

   Use parentheses to control label logic = C [OK]

Hint: Use parentheses to clarify label logic precedence [OK]

Common Mistakes:

• Ignoring operator precedence in label expressions
• Using wrong quote types
• Believing logical operators are not allowed

5.

You want a Jenkins job to run only on agents that have linux and docker labels but never on agents with gpu label. Which label expression should you use?

hard

A. linux && docker && !gpu

B. linux && docker || !gpu

C. linux && (docker || !gpu)

D. linux && docker && gpu

Solution

1. Step 1: Understand label requirements

   The job must run on agents with both 'linux' and 'docker' labels, but exclude any with 'gpu'.

2. Step 2: Construct correct label expression

   Use AND (&&) for required labels and NOT (!) to exclude 'gpu': 'linux && docker && !gpu'.

3. Final Answer:

   linux && docker && !gpu -> Option A

4. Quick Check:

   Include linux and docker, exclude gpu = B [OK]

Hint: Use ! to exclude labels in Jenkins expressions [OK]

Common Mistakes:

• Using OR instead of AND for required labels
• Not excluding gpu label properly
• Misplacing parentheses causing wrong logic