Agent types (permanent, cloud) in Jenkins - Mini Project: Build & Apply

Jenkins Agent Types: Permanent and Cloud Agents

📖 Scenario: You are setting up a Jenkins server to run automated jobs. Jenkins uses agents (also called nodes) to run these jobs. There are two main types of agents: permanent agents that are always available, and cloud agents that start on demand in the cloud.Understanding how to configure these agents helps you manage your build resources efficiently.

🎯 Goal: Learn to create a permanent Jenkins agent configuration and a cloud agent configuration using Jenkins pipeline syntax. You will define the agents and then run a simple job on each type.

📋 What You'll Learn

Create a permanent agent configuration in Jenkins pipeline

Create a cloud agent configuration in Jenkins pipeline

Use the agent directive correctly for both types

Run a simple shell command on each agent to verify setup

💡 Why This Matters

🌍 Real World

In real Jenkins setups, permanent agents are often physical or virtual machines always connected to Jenkins. Cloud agents are created on demand in cloud platforms like AWS or Azure to save resources.

💼 Career

Knowing how to configure different agent types helps DevOps engineers optimize build times and resource usage in continuous integration and delivery pipelines.

1

Create a permanent agent configuration

Write a Jenkins pipeline script that uses a permanent agent labeled permanent-agent. Inside the stage named Build, run the shell command echo "Running on permanent agent".

Jenkins

pipeline {
    agent { label 'permanent-agent' }
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Hint

Use agent { label 'permanent-agent' } to specify the permanent agent.

Use sh 'echo "Running on permanent agent"' inside the steps block.

2

Add a cloud agent configuration variable

Add a variable called cloudAgentLabel and set it to the string 'cloud-agent' at the top of the Jenkins pipeline script.

Jenkins

def cloudAgentLabel = 'cloud-agent'

pipeline {
    agent { label 'permanent-agent' }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Running on permanent agent"'
            }
        }
    }
}

// Your code here

Hint

Define cloudAgentLabel as 'cloud-agent' before the pipeline block.

3

Add a stage to run on the cloud agent

Add a new stage named Test on Cloud Agent inside the stages block. Use the agent directive with the label set to the variable cloudAgentLabel. Inside the steps, run the shell command echo "Running on cloud agent".

Jenkins

def cloudAgentLabel = 'cloud-agent'

pipeline {
    agent { label 'permanent-agent' }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Running on permanent agent"'
            }
        }
        // Your code here
    }
}

Hint

Inside stages, add a new stage with agent { label cloudAgentLabel } and the shell command inside steps.

4

Print confirmation messages for both agents

Add a post block inside the pipeline that runs echo "Pipeline completed successfully" in the always section.

Jenkins

def cloudAgentLabel = 'cloud-agent'

pipeline {
    agent { label 'permanent-agent' }
    stages {
        stage('Build') {
            steps {
                sh 'echo "Running on permanent agent"'
            }
        }
        stage('Test on Cloud Agent') {
            agent { label cloudAgentLabel }
            steps {
                sh 'echo "Running on cloud agent"'
            }
        }
    }
    // Your code here
}

Hint

Use a post block with always to print the confirmation message.

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