Cloud agent provisioning (EC2, Azure) in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a cloud agent in Jenkins?

A cloud agent in Jenkins is a virtual machine or container that Jenkins provisions dynamically in the cloud (like EC2 or Azure) to run build jobs. It helps scale build capacity on demand.

beginner

Name two popular cloud providers Jenkins can provision agents from.

Amazon EC2 (Elastic Compute Cloud) and Microsoft Azure are two popular cloud providers Jenkins can use to provision agents dynamically.

intermediate

What Jenkins plugin is commonly used to provision EC2 agents?

The 'Amazon EC2 Plugin' is commonly used in Jenkins to provision EC2 instances as build agents automatically.

intermediate

How does Jenkins authenticate to Azure to provision agents?

Jenkins uses Azure service principal credentials (client ID, secret, tenant ID) to authenticate and provision Azure virtual machines as agents.

beginner

Why use cloud agent provisioning instead of static agents?

Cloud agent provisioning allows Jenkins to create agents only when needed, saving costs and resources by not running idle machines all the time.

Which Jenkins plugin helps provision EC2 instances as build agents?

A Amazon EC2 Plugin

B Azure VM Agents Plugin

C Docker Plugin

D Kubernetes Plugin

The Amazon EC2 Plugin is designed specifically to provision EC2 instances as Jenkins agents.

What credentials does Jenkins need to provision Azure agents?

A SSH key only

B AWS access key and secret

C GitHub personal access token

D Azure service principal credentials

Jenkins uses Azure service principal credentials (client ID, secret, tenant ID) to authenticate and create Azure VMs.

What is a key benefit of using cloud agent provisioning in Jenkins?

A Agents run only when needed, saving cost

B Agents never need updates

C Agents are always offline

D Agents use physical hardware only

Cloud agents are created on demand, so you pay only for what you use.

Which cloud provider is NOT typically used for Jenkins cloud agents?

A Amazon EC2

B Microsoft Azure

C Local desktop

D Google Cloud Platform

Local desktops are not cloud providers and are not used for dynamic cloud agent provisioning.

What is the first step to enable EC2 agent provisioning in Jenkins?

A Create a Jenkins pipeline

B Install the Amazon EC2 Plugin

C Write a Dockerfile

D Configure GitHub webhook

You must install the Amazon EC2 Plugin to enable EC2 agent provisioning.

Explain how Jenkins provisions a cloud agent on EC2.

Think about the plugin, authentication, instance launch, and lifecycle.

Describe the steps to configure Jenkins to provision agents on Azure.

Focus on authentication, plugin, and VM template setup.

Practice

1. What is the main purpose of cloud agent provisioning in Jenkins?

easy

A. To dynamically create and use cloud machines as Jenkins agents

B. To manually configure Jenkins agents on local machines

C. To backup Jenkins configuration files to the cloud

D. To monitor Jenkins job execution times

Solution

1. Step 1: Understand Jenkins agent provisioning

   Jenkins can create agents dynamically in the cloud to run jobs without manual setup.

2. Step 2: Identify the purpose of cloud provisioning

   Cloud agent provisioning automates creating cloud machines (like EC2 or Azure VMs) as Jenkins agents.

3. Final Answer:

   To dynamically create and use cloud machines as Jenkins agents -> Option A

4. Quick Check:

   Cloud agent provisioning = dynamic cloud agents [OK]

Hint: Cloud provisioning means automatic cloud agent creation [OK]

Common Mistakes:

• Confusing provisioning with manual setup
• Thinking it is for backup or monitoring
• Assuming it only works on local machines

2. Which of the following is the correct way to specify an EC2 AMI ID in Jenkins cloud agent configuration?

easy

A. ami-0abcdef1234567890

B. ec2-ami-123456

C. AMI:1234567890

D. image-ec2-abcdef

Solution

1. Step 1: Recognize EC2 AMI ID format

   EC2 AMI IDs start with 'ami-' followed by alphanumeric characters, e.g., 'ami-0abcdef1234567890'.

2. Step 2: Match the correct format

   ami-0abcdef1234567890 matches the standard EC2 AMI ID format exactly.

3. Final Answer:

   ami-0abcdef1234567890 -> Option A

4. Quick Check:

   EC2 AMI ID starts with 'ami-' [OK]

Hint: EC2 AMI IDs always start with 'ami-' [OK]

Common Mistakes:

• Using incorrect prefixes like 'ec2-ami-'
• Confusing AMI ID with image names
• Adding extra labels or colons

3. Given this Jenkins EC2 cloud agent snippet:

instanceCapStr: '3',
idleTerminationMinutes: 10,
ami: 'ami-0abc123def456',
remoteFS: '/home/jenkins'

What happens when 4 jobs are triggered simultaneously?

medium

A. Jenkins throws an error due to instance cap mismatch

B. 4 agents will be created ignoring the instance cap

C. All 4 jobs run on a single agent

D. Only 3 agents will be created; the 4th job waits in queue

Solution

1. Step 1: Understand instanceCapStr meaning

   The 'instanceCapStr' limits the max number of EC2 agents Jenkins can create to 3.

2. Step 2: Analyze job triggering behavior

   When 4 jobs start, Jenkins creates only 3 agents due to the cap; the 4th job waits in the queue.

3. Final Answer:

   Only 3 agents will be created; the 4th job waits in queue -> Option D

4. Quick Check:

   Instance cap limits agents = jobs queue if exceeded [OK]

Hint: Instance cap limits agents; extra jobs queue [OK]

Common Mistakes:

• Assuming Jenkins ignores instance cap
• Thinking all jobs run on one agent
• Expecting an error when cap exceeded

4. You configured an Azure cloud agent in Jenkins but agents never start. Which is the most likely cause?

medium

A. Instance cap set to zero

B. Jenkins master is offline

C. Incorrect Azure VM image name or ID

D. Idle timeout set too high

Solution

1. Step 1: Check Azure VM image configuration

   If the VM image name or ID is wrong, Jenkins cannot provision agents on Azure.

2. Step 2: Evaluate other options

   Jenkins master offline stops all jobs, but question focuses on agent provisioning. Instance cap zero means no agents, but usually agents would not start at all. Idle timeout affects termination, not start.

3. Final Answer:

   Incorrect Azure VM image name or ID -> Option C

4. Quick Check:

   Wrong VM image blocks agent start [OK]

Hint: Check VM image name first if agents don't start [OK]

Common Mistakes:

• Ignoring VM image correctness
• Blaming idle timeout for start issues
• Assuming Jenkins master offline without checking

5. You want to optimize Jenkins cloud agents on EC2 to reduce cost. Which combination of settings is best?

hard

A. Set instance cap high and idle termination to 60 minutes

B. Set instance cap low and idle termination to 5 minutes

C. Disable instance cap and idle termination

D. Set instance cap low and disable idle termination

Solution

1. Step 1: Understand instance cap effect

   A low instance cap limits max running agents, controlling cloud costs.

2. Step 2: Understand idle termination effect

   Setting idle termination to 5 minutes stops unused agents quickly, saving cost.

3. Step 3: Evaluate other options

   High cap or disabling termination increases cost. Disabling termination wastes resources.

4. Final Answer:

   Set instance cap low and idle termination to 5 minutes -> Option B

5. Quick Check:

   Low cap + quick termination = cost saving [OK]

Hint: Low cap + short idle timeout saves cloud cost [OK]

Common Mistakes:

• Setting high caps wastes money
• Disabling idle termination keeps idle agents running
• Ignoring cost impact of settings