Agent availability and offline handling in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Jenkins Agent Offline Causes

Which of the following is NOT a common reason for a Jenkins agent to go offline?

A Agent is configured with an incorrect label

B Agent machine running out of disk space

C Jenkins master running out of memory

D Network connectivity issues between the master and the agent

💡 Hint

Think about what causes communication failure versus configuration mismatches.

Incorrect labels do not cause the agent to go offline; they only affect job assignment. Offline status usually results from communication or resource issues.

💻 Command Output

intermediate

Jenkins CLI Agent Offline Status Command Output

What is the output of the following Jenkins CLI command when the agent named 'build-agent-1' is offline?

java -jar jenkins-cli.jar -s http://jenkins.example.com/ list-agents

A build-agent-1 (offline)

B build-agent-1 (online)

C Error: Agent build-agent-1 not found

D build-agent-1 (idle)

💡 Hint

Offline agents are usually marked explicitly in the list.

The CLI lists agents with their status; offline agents are shown with '(offline)'.

❓ Configuration

advanced

Configuring Jenkins Agent to Automatically Reconnect

Which configuration snippet in the Jenkins agent launch method ensures the agent automatically tries to reconnect if disconnected?

A java -jar agent.jar -jnlpUrl http://jenkins.example.com/computer/agent/slave-agent.jnlp -workDir "/home/jenkins/agent"

B java -jar agent.jar -jnlpUrl http://jenkins.example.com/computer/agent/slave-agent.jnlp -workDir "/home/jenkins/agent" -noReconnect

C java -jar agent.jar -jnlpUrl http://jenkins.example.com/computer/agent/slave-agent.jnlp -workDir "/home/jenkins/agent" -retry 5

D java -jar agent.jar -jnlpUrl http://jenkins.example.com/computer/agent/slave-agent.jnlp -workDir "/home/jenkins/agent" -retry 0

💡 Hint

Look for options that control retry or reconnect behavior.

The '-retry 5' option tells the agent to retry connection 5 times automatically.

❓ Troubleshoot

advanced

Diagnosing Jenkins Agent Offline Due to Firewall

A Jenkins agent suddenly goes offline. The agent machine's firewall was recently updated. Which troubleshooting step is most effective to confirm if the firewall is causing the offline status?

A Check Jenkins master logs for connection timeout errors

B Temporarily disable the firewall on the agent machine and try reconnecting

C Restart the Jenkins master service

D Reboot the agent machine

💡 Hint

Think about isolating the firewall as the cause.

Disabling the firewall temporarily helps confirm if it blocks the agent connection.

🔀 Workflow

expert

Handling Jenkins Agent Offline in a CI/CD Pipeline

In a Jenkins pipeline, you want to ensure that if the assigned agent goes offline during a build, the pipeline automatically retries on another available agent. Which pipeline script snippet correctly implements this behavior?

A

pipeline {
  agent { label 'linux' }
  stages { stage('Build') { steps { echo 'Building...' } } }
  options { skipDefaultCheckout() }
}

B

pipeline {
  agent any
  options { retry(3) }
  stages { stage('Build') { steps { echo 'Building...' } } }
}

C

pipeline {
  agent { label 'linux' }
  stages { stage('Build') { steps { echo 'Building...' } } }
  post { failure { retry(3) { echo 'Retrying build...' } } }
}

D

pipeline {
  agent { label 'linux' }
  stages { stage('Build') { steps { retry(3) { echo 'Building...' } } } }
}

💡 Hint

Look for retry inside the build steps to retry on failure.

Placing retry inside the steps block retries the build steps on failure, including agent offline errors, on another agent matching the label.

Practice

1. What does it mean when a Jenkins agent is marked as offline?

easy

A. The agent is connected and ready to accept jobs.

B. The agent is not available to run any jobs.

C. The agent is running a job currently.

D. The agent is permanently deleted from Jenkins.

Solution

1. Step 1: Understand agent status meaning

   In Jenkins, an agent marked offline means it is not available to run jobs.

2. Step 2: Differentiate from other statuses

   Online agents are connected and ready; offline means unavailable temporarily or for maintenance.

3. Final Answer:

   The agent is not available to run any jobs. -> Option B

4. Quick Check:

   Offline agent = unavailable [OK]

Hint: Offline means agent can't run jobs now [OK]

Common Mistakes:

• Confusing offline with running a job
• Thinking offline means deleted
• Assuming offline means ready

2. Which of the following is the correct way to mark a Jenkins agent as offline using the Jenkins CLI?

easy

A. jenkins-cli offline-agent --name agent1

B. java -jar jenkins-cli.jar offline-agent agent1

C. java -jar jenkins-cli.jar offline-agent --agent agent1

D. java -jar jenkins-cli.jar disconnect-node agent1

Solution

1. Step 1: Recall Jenkins CLI command for offline

   The correct command to mark an agent offline is disconnect-node with the agent name as argument.

2. Step 2: Check syntax correctness

   Options A, B, and C use incorrect commands or flags; only java -jar jenkins-cli.jar disconnect-node agent1 uses the correct command and syntax.

3. Final Answer:

   java -jar jenkins-cli.jar disconnect-node agent1 -> Option D

4. Quick Check:

   disconnect-node command marks offline [OK]

Hint: Use 'disconnect-node' command with agent name [OK]

Common Mistakes:

• Using wrong command names like offline-agent
• Adding incorrect flags
• Confusing CLI syntax

3. Given this Jenkins pipeline snippet:

node('agent1') {
  echo "Agent status: ${env.NODE_NAME}"
}

If agent1 is offline, what will happen when this pipeline runs?

medium

A. The pipeline will fail immediately with an error.

B. The pipeline will run on the master node instead.

C. The pipeline will wait until agent1 comes online.

D. The pipeline will skip the node block and continue.

Solution

1. Step 1: Understand node block behavior

   The node('agent1') block waits for the specified agent to be available before running.

2. Step 2: Check what happens if agent is offline

   If agent1 is offline, Jenkins will wait until it comes online or timeout occurs.

3. Final Answer:

   The pipeline will wait until agent1 comes online. -> Option C

4. Quick Check:

   node waits for agent online [OK]

Hint: node waits for specified agent to be online [OK]

Common Mistakes:

• Assuming pipeline fails immediately
• Thinking it runs on master automatically
• Believing it skips the node block

4. You have a Jenkins agent that should be offline for maintenance, but jobs are still assigned to it. What is the most likely cause?

medium

A. The agent was not properly marked offline in Jenkins configuration.

B. The agent is offline but Jenkins is ignoring the status due to a plugin bug.

C. The agent was marked offline but the 'Accept tasks' option is still enabled.

D. The jobs are configured to run only on the master node.

Solution

1. Step 1: Check agent offline marking

   If jobs are still assigned, likely the agent was not properly marked offline in Jenkins UI or configuration.

2. Step 2: Eliminate other causes

   The agent was marked offline but the 'Accept tasks' option is still enabled. is incorrect because offline agents do not accept tasks; The agent is offline but Jenkins is ignoring the status due to a plugin bug. is rare; The jobs are configured to run only on the master node. is unrelated.

3. Final Answer:

   The agent was not properly marked offline in Jenkins configuration. -> Option A

4. Quick Check:

   Proper offline marking stops job assignment [OK]

Hint: Ensure agent is correctly marked offline in Jenkins UI [OK]

Common Mistakes:

• Assuming offline agent still accepts tasks
• Blaming plugins without checking config
• Confusing job node assignment

5. You want to create a Jenkins pipeline that automatically skips running on an agent if it is offline and instead runs on the master node. Which scripted pipeline snippet achieves this?

hard

A. if (Jenkins.instance.getNode('agent1').toComputer().isOnline()) {
node('agent1') { echo 'Running on agent1' }
} else {
node('master') { echo 'Running on master' }
}

B. node('agent1') {
if (agent1.isOnline()) {
echo 'Running on agent1'
} else {
node('master') { echo 'Running on master' }
}
}

C. try {
node('agent1') { echo 'Running on agent1' }
} catch (Exception e) {
node('master') { echo 'Running on master' }
}

D. node('agent1') {
echo 'Running on agent1'
}
node('master') {
echo 'Running on master'
}

Solution

1. Step 1: Check agent online status in pipeline

   if (Jenkins.instance.getNode('agent1').toComputer().isOnline()) { node('agent1') { echo 'Running on agent1' } } else { node('master') { echo 'Running on master' } } correctly checks if 'agent1' is online using Jenkins API before choosing node.

2. Step 2: Verify fallback to master node

   If agent1 is offline, if (Jenkins.instance.getNode('agent1').toComputer().isOnline()) { node('agent1') { echo 'Running on agent1' } } else { node('master') { echo 'Running on master' } } runs the job on 'master' node, matching the requirement.

3. Step 3: Analyze other options

   node('agent1') { if (agent1.isOnline()) { echo 'Running on agent1' } else { node('master') { echo 'Running on master' } } } uses invalid syntax; try { node('agent1') { echo 'Running on agent1' } } catch (Exception e) { node('master') { echo 'Running on master' } } relies on exception which is not best practice; node('agent1') { echo 'Running on agent1' } node('master') { echo 'Running on master' } runs both nodes unconditionally.

4. Final Answer:

   if (Jenkins.instance.getNode('agent1').toComputer().isOnline()) { node('agent1') { echo 'Running on agent1' } } else { node('master') { echo 'Running on master' } } -> Option A

5. Quick Check:

   Check agent online status before node selection [OK]

Hint: Check agent online status via Jenkins API before node [OK]

Common Mistakes:

• Using invalid syntax to check agent status
• Relying on exceptions to handle offline agents
• Running both nodes regardless of status