Agent types (permanent, cloud) in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a permanent agent in Jenkins?

A permanent agent is a Jenkins node that is always available and manually configured. It runs on a fixed machine and stays connected to the Jenkins master unless manually disconnected.

beginner

What defines a cloud agent in Jenkins?

A cloud agent is a temporary Jenkins node created dynamically on cloud infrastructure. It spins up when needed for a job and is destroyed after the job finishes.

intermediate

How does a cloud agent help optimize resources?

Cloud agents only run when jobs need them, so they save resources by not running all the time. This reduces costs and improves scalability.

beginner

Name one key difference between permanent and cloud agents.

Permanent agents are always running and connected, while cloud agents are created and destroyed dynamically based on job demand.

intermediate

Why might a team choose permanent agents over cloud agents?

Teams might choose permanent agents for stable, long-running environments or when cloud infrastructure is not available or too costly.

What happens to a cloud agent after a Jenkins job finishes?

A It disconnects but stays on the machine

B It stays running indefinitely

C It becomes a permanent agent

D It is destroyed to save resources

Cloud agents are temporary and are destroyed after the job completes to optimize resource use.

Which agent type requires manual setup and stays connected to Jenkins?

A Permanent agent

B Dynamic agent

C Ephemeral agent

D Cloud agent

Permanent agents are manually configured and remain connected to Jenkins until manually disconnected.

What is a main benefit of using cloud agents in Jenkins?

A They reduce infrastructure costs by running only when needed

B They provide permanent storage for builds

C They require no network connection

D They run on the Jenkins master machine

Cloud agents spin up on demand and shut down after use, saving infrastructure costs.

Which Jenkins agent type is best for long-running, stable workloads?

A Cloud agent

B Permanent agent

C Temporary agent

D Serverless agent

Permanent agents are suited for stable workloads because they stay connected and ready.

How does Jenkins typically create cloud agents?

A By cloning permanent agents

B Manually by the admin

C Automatically via cloud plugins when jobs start

D By running on the Jenkins master

Jenkins uses cloud plugins to automatically provision cloud agents when jobs require them.

Explain the differences between permanent and cloud agents in Jenkins.

Think about availability and resource management.

Describe a scenario where using a cloud agent is better than a permanent agent.

Consider cost and scalability benefits.

Practice

1. What is a key characteristic of a permanent agent in Jenkins?

easy

A. It runs only on cloud platforms like AWS or Azure.

B. It is always connected and ready to run jobs.

C. It starts only when a job is triggered and stops afterward.

D. It automatically scales based on job demand.

Solution

1. Step 1: Understand permanent agent behavior

   Permanent agents are set up to be always online and ready to accept jobs without delay.

2. Step 2: Compare with cloud agents

   Cloud agents start and stop dynamically, unlike permanent agents which stay connected.

3. Final Answer:

   It is always connected and ready to run jobs. -> Option B

4. Quick Check:

   Permanent agent = always connected [OK]

Hint: Permanent agents stay online; cloud agents start/stop [OK]

Common Mistakes:

• Confusing permanent agents with cloud agents
• Thinking permanent agents scale automatically
• Assuming permanent agents only run on cloud

2. Which of the following is the correct way to define a cloud agent in Jenkins pipeline syntax?

easy

A. agent { permanent { name 'agent1' } }

B. agent { cloud { cloudName 'aws' } }

C. agent { docker { image 'cloud-agent' } }

D. agent { label 'cloud' }

Solution

1. Step 1: Identify cloud agent syntax

   Jenkins pipeline uses agent { label 'cloud' } to target cloud agents provisioned with matching labels.

2. Step 2: Eliminate other options

   agent { cloud { cloudName 'aws' } } is invalid syntax; C is for Docker agents, not cloud agents; D is incorrect syntax.

3. Final Answer:

   agent { label 'cloud' } -> Option D

4. Quick Check:

   Cloud agent syntax uses label { 'cloud' } [OK]

Hint: Cloud agents use agent { label 'cloud' } [OK]

Common Mistakes:

• Using invalid 'cloud { cloudName }' syntax for cloud agents
• Confusing Docker agent syntax with cloud agent
• Trying to define permanent agents inside agent block

3. Given this Jenkinsfile snippet:

pipeline {
  agent { label 'cloud' }
  stages {
    stage('Build') {
      steps {
        echo 'Running on cloud agent'
      }
    }
  }
}

What will happen when this pipeline runs?

medium

A. It fails because 'cloud' label is invalid for agents.

B. It runs on a permanent agent labeled 'cloud'.

C. It runs on a cloud agent that starts and stops automatically.

D. It runs on the master node regardless of label.

Solution

1. Step 1: Understand label usage

   The pipeline requests an agent with label 'cloud', which typically refers to a cloud agent.

2. Step 2: Behavior of cloud agents

   Cloud agents start when needed and stop after the job finishes, matching the label usage.

3. Final Answer:

   It runs on a cloud agent that starts and stops automatically. -> Option C

4. Quick Check:

   Label 'cloud' triggers cloud agent start/stop [OK]

Hint: Label 'cloud' usually means dynamic cloud agent [OK]

Common Mistakes:

• Assuming label 'cloud' means permanent agent
• Thinking label usage causes failure
• Assuming master node runs all jobs

4. You configured a cloud agent in Jenkins, but jobs never run on it and stay queued. What is the most likely cause?

medium

A. The cloud agent label is missing or mismatched in the job configuration.

B. The permanent agent is offline, so cloud agents cannot start.

C. The Jenkins master node is overloaded and blocking all agents.

D. The cloud agent plugin is not installed, causing syntax errors.

Solution

1. Step 1: Check label matching

   Jobs must specify the correct label matching the cloud agent to run on it.

2. Step 2: Understand job-agent assignment

   If labels don't match, Jenkins queues jobs waiting for suitable agents.

3. Final Answer:

   The cloud agent label is missing or mismatched in the job configuration. -> Option A

4. Quick Check:

   Label mismatch causes jobs to queue [OK]

Hint: Always match job label with agent label [OK]

Common Mistakes:

• Assuming permanent agent status affects cloud agents
• Blaming Jenkins master overload without evidence
• Confusing plugin absence with job queuing

5. You want to optimize Jenkins to save resources by using cloud agents for most jobs but keep a permanent agent for critical builds. How should you configure labels and agents?

hard

A. Assign label 'critical' to the permanent agent and 'cloud' to cloud agents; assign jobs accordingly.

B. Use only permanent agents with label 'all' and avoid cloud agents to reduce complexity.

C. Assign all jobs to label 'cloud' and disable the permanent agent to save resources.

D. Configure cloud agents without labels and assign all jobs to the permanent agent.

Solution

1. Step 1: Separate job types by labels

   Use distinct labels like 'critical' for permanent agent and 'cloud' for cloud agents to control job assignment.

2. Step 2: Assign jobs to matching labels

   Critical builds use the permanent agent with 'critical' label; other jobs use cloud agents with 'cloud' label.

3. Final Answer:

   Assign label 'critical' to the permanent agent and 'cloud' to cloud agents; assign jobs accordingly. -> Option A

4. Quick Check:

   Use labels to separate permanent and cloud jobs [OK]

Hint: Label agents and jobs to control resource use [OK]

Common Mistakes:

• Using only one label for all agents
• Disabling permanent agent when critical builds exist
• Not assigning labels to cloud agents