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.