Master-agent architecture in Jenkins - Mini Project: Build & Apply

Master-agent architecture

📖 Scenario: You are setting up a Jenkins environment to automate software builds. Jenkins uses a master-agent architecture where the master controls the build process and agents run the build jobs.In this project, you will create a simple Jenkins pipeline script that defines the master and an agent node to run a build step.

🎯 Goal: Build a Jenkins pipeline script that specifies a master and an agent node, then runs a simple shell command on the agent.

📋 What You'll Learn

Create a Jenkins pipeline with a pipeline block

Define an agent with label linux

Add a stage named Build

Inside the stage, run a shell command echo "Building on agent"

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software builds and tests by distributing work from the master to multiple agent nodes.

💼 Career

Understanding master-agent architecture is essential for DevOps engineers to set up scalable CI/CD pipelines.

1

Create the pipeline block

Write a Jenkins pipeline script starting with pipeline {} block.

Jenkins

pipeline {
    // Your code here
}

Hint

The pipeline block is the root of your Jenkinsfile script.

2

Add an agent with label linux

Inside the pipeline block, add an agent section with label 'linux' to specify the agent node.

Jenkins

pipeline {
    agent {
        // Your code here
    }
}

Hint

The agent label tells Jenkins which node to run the build on.

3

Add a Build stage with a shell step

Inside the pipeline block, add a stages section with one stage named Build. Inside this stage, add a steps block that runs the shell command echo "Building on agent" using sh.

Jenkins

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

Hint

The sh step runs shell commands on the agent node.

4

Print the pipeline script

Print the entire Jenkins pipeline script you wrote.

Jenkins

// Your code here to print the pipeline script

Hint

Use println to output confirmation text.

Practice

1. What is the main role of the Jenkins master in the master-agent architecture?

easy

A. To run jobs on different machines

B. To control and schedule jobs

C. To store job logs only

D. To act as a backup server

Solution

1. Step 1: Understand the master role

   The Jenkins master is responsible for controlling and scheduling jobs, meaning it decides when and where jobs run.

2. Step 2: Differentiate from agent role

   Agents actually run the jobs on separate machines, not the master.

3. Final Answer:

   To control and schedule jobs -> Option B

4. Quick Check:

   Master controls jobs = B [OK]

Hint: Master schedules jobs; agents run them [OK]

Common Mistakes:

• Confusing master with agent role
• Thinking master runs jobs directly
• Assuming master only stores logs

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

easy

A. run agent

B. master agent

C. agent any

D. node master

Solution

1. Step 1: Recall Jenkins pipeline syntax

   In Jenkins declarative pipeline, agent any means the job can run on any available agent.

2. Step 2: Check other options

   Options like master agent, run agent, and node master are not valid syntax for defining agents.

3. Final Answer:

   agent any -> Option C

4. Quick Check:

   Correct agent syntax = A [OK]

Hint: Use 'agent any' to run on any available agent [OK]

Common Mistakes:

• Using invalid keywords like 'master agent'
• Confusing 'node' with 'agent'
• Writing 'run agent' which is not valid

3. Given this Jenkins pipeline snippet, what will happen?

pipeline {
  agent { label 'linux' }
  stages {
    stage('Build') {
      steps {
        echo 'Building on Linux agent'
      }
    }
  }
}

medium

A. The job runs on any available agent

B. The job runs on the master node

C. The job fails due to syntax error

D. The job runs on an agent labeled 'linux'

Solution

1. Step 1: Analyze the agent label

   The pipeline specifies agent { label 'linux' }, so it will run on an agent with the label 'linux'.

2. Step 2: Understand job execution

   Since the label is specific, the job will not run on any agent or the master unless they have that label.

3. Final Answer:

   The job runs on an agent labeled 'linux' -> Option D

4. Quick Check:

   Agent label 'linux' = C [OK]

Hint: Agent label selects specific machine for job [OK]

Common Mistakes:

• Assuming 'agent any' runs here
• Thinking job runs on master by default
• Believing syntax causes failure

4. You configured an agent but Jenkins shows it as offline. What is the most likely cause?

medium

A. Agent machine is turned off or unreachable

B. Master node is overloaded

C. Pipeline syntax error in Jenkinsfile

D. Agent label does not match any job

Solution

1. Step 1: Understand agent offline status

   An agent shows offline if Jenkins cannot connect to it, often because the machine is off or network unreachable.

2. Step 2: Eliminate other causes

   Master overload or pipeline syntax errors do not cause agent offline status. Label mismatch prevents job assignment but does not make agent offline.

3. Final Answer:

   Agent machine is turned off or unreachable -> Option A

4. Quick Check:

   Offline agent = unreachable machine [OK]

Hint: Offline agent means machine unreachable or off [OK]

Common Mistakes:

• Blaming master overload for offline agent
• Confusing syntax errors with connectivity
• Thinking label mismatch causes offline

5. How can you improve Jenkins performance when running many jobs simultaneously using master-agent architecture?

hard

A. Add more agents to distribute the workload

B. Run all jobs on the master node to avoid delays

C. Disable agents to reduce network traffic

D. Use only one agent with high CPU

Solution

1. Step 1: Understand workload distribution

   Adding more agents allows Jenkins to run jobs in parallel on different machines, improving performance.

2. Step 2: Evaluate other options

   Running all jobs on master overloads it, disabling agents reduces capacity, and one agent limits parallelism.

3. Final Answer:

   Add more agents to distribute the workload -> Option A

4. Quick Check:

   More agents = better parallel job handling [OK]

Hint: More agents mean faster job execution [OK]

Common Mistakes:

• Overloading master with all jobs
• Disabling agents thinking it helps
• Relying on single powerful agent only