Performance tuning in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the Jenkins executor count to improve parallel builds.

Jenkins

jenkins.model.Jenkins.instance.setNumExecutors([1])

Drag options to blanks, or click blank then click option'

A0

B5

C-1

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Setting executors to 0 disables builds.

Negative numbers cause errors.

Setting the number of executors to 10 allows Jenkins to run 10 builds in parallel, improving performance.

2fill in blank

medium

Complete the code to enable the Jenkins build queue to timeout after a certain period.

Jenkins

jenkins.model.Jenkins.instance.getQueue().setBuildableTimeout([1])

Drag options to blanks, or click blank then click option'

A600000

B30000

C0

D-100

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero disables timeout.

Negative values cause errors.

600000 milliseconds (10 minutes) sets a reasonable timeout for build queue items to wait before timing out.

3fill in blank

hard

Fix the error in the code to properly set the Jenkins system message for performance monitoring.

Jenkins

jenkins.model.Jenkins.instance.setSystemMessage([1])

Drag options to blanks, or click blank then click option'

APerformance tuning enabled

B"Performance tuning enabled"

CPerformance tuning enabled;

D'Performance tuning enabled'

Attempts:

3 left

💡 Hint

Common Mistakes

Missing quotes cause syntax errors.

Adding semicolons is unnecessary here.

The system message must be a string, so it needs to be enclosed in double quotes.

4fill in blank

hard

Fill both blanks to create a map of job names to their last build duration in milliseconds.

Jenkins

def durations = jenkins.model.Jenkins.instance.getAllItems().collectEntries { job -> [job.[1], job.getLastBuild()?.[2] ?: 0] }

Drag options to blanks, or click blank then click option'

Aname

Bduration

Ctimestamp

DgetDuration

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'duration' property directly causes errors.

Using 'timestamp' gives build start time, not duration.

Use 'name' to get the job name and 'getDuration' method to get the last build duration.

5fill in blank

hard

Fill all three blanks to filter jobs with last build duration greater than 5 minutes and create a map of job names to durations.

Jenkins

def slowJobs = jenkins.model.Jenkins.instance.getAllItems().findAll { job -> job.getLastBuild()?.[1] ?: 0 [2] [3] } .collectEntries { job -> [job.name, job.getLastBuild().getDuration()] }

Drag options to blanks, or click blank then click option'

AgetDuration()

B>

C300000

Dduration

Attempts:

3 left

💡 Hint

Common Mistakes

Using property 'duration' instead of method causes errors.

Using '<' instead of '>' reverses the filter.

Use 'getDuration()' to get build duration, '>' to compare, and 300000 milliseconds (5 minutes) as the threshold.

Practice

1. What is the main purpose of performance tuning in Jenkins?

easy

A. To make Jenkins faster and more reliable

B. To add more plugins to Jenkins

C. To change the Jenkins user interface

D. To increase the number of users who can log in

Solution

1. Step 1: Understand performance tuning goal

   Performance tuning aims to improve speed and reliability of Jenkins.

2. Step 2: Identify correct purpose

   Adding plugins or changing UI does not directly improve performance.

3. Final Answer:

   To make Jenkins faster and more reliable -> Option A

4. Quick Check:

   Performance tuning = faster, reliable Jenkins [OK]

Hint: Performance tuning improves speed and reliability [OK]

Common Mistakes:

• Confusing UI changes with performance tuning
• Thinking adding plugins always improves speed
• Assuming user count affects performance tuning

2. Which Jenkins configuration setting directly controls how many builds can run at the same time on a node?

easy

A. Number of executors

B. Build timeout

C. Build discard policy

D. Workspace cleanup

Solution

1. Step 1: Identify setting for parallel builds

   The number of executors defines how many builds run concurrently on a node.

2. Step 2: Eliminate unrelated options

   Build timeout stops builds after time, discard policy deletes old builds, workspace cleanup removes files.

3. Final Answer:

   Number of executors -> Option A

4. Quick Check:

   Executors = parallel build slots [OK]

Hint: Executors control parallel builds on a node [OK]

Common Mistakes:

• Confusing build timeout with executors
• Mixing discard policy with concurrency
• Thinking workspace cleanup affects build count

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

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        parallel {
          stage('Test1') { steps { echo 'Running Test1' } }
          stage('Test2') { steps { echo 'Running Test2' } }
        }
      }
    }
  }
}

medium

A. Test1 and Test2 run one after the other

B. Pipeline fails due to syntax error

C. Test1 and Test2 run at the same time

D. Only Test1 runs

Solution

1. Step 1: Understand parallel block in pipeline

   The parallel block runs multiple stages simultaneously.

2. Step 2: Analyze given stages

   Test1 and Test2 are inside parallel, so both run at the same time.

3. Final Answer:

   Test1 and Test2 run at the same time -> Option C

4. Quick Check:

   parallel block = simultaneous stages [OK]

Hint: parallel block runs stages simultaneously [OK]

Common Mistakes:

• Assuming stages run sequentially by default
• Thinking only one parallel stage runs
• Believing syntax error exists in pipeline

4. You notice Jenkins is slow and builds queue up. Which configuration mistake could cause this?

medium

A. Increasing build retention days

B. Setting number of executors to 1 on a powerful node

C. Enabling parallel pipelines

D. Using lightweight checkout

Solution

1. Step 1: Identify cause of slow builds and queue

   Having only 1 executor limits concurrent builds, causing queue.

2. Step 2: Check other options

   Parallel pipelines improve speed, retention affects storage, lightweight checkout reduces load.

3. Final Answer:

   Setting number of executors to 1 on a powerful node -> Option B

4. Quick Check:

   Too few executors = slow builds [OK]

Hint: Few executors cause build queue delays [OK]

Common Mistakes:

• Thinking parallel pipelines slow Jenkins
• Confusing build retention with performance
• Ignoring executor count impact

5. To improve Jenkins performance on a server with 16GB RAM and 8 CPU cores, which combination is best?

hard

A. Set executors to 4, disable parallel pipelines, and increase build retention days

B. Set executors to 1, disable parallel pipelines, and reduce JVM heap memory

C. Set executors to 16, disable parallel pipelines, and keep default JVM memory

D. Set executors to 8, enable parallel pipelines, and increase JVM heap memory

Solution

1. Step 1: Match executors to CPU cores

   Setting executors to 8 uses all CPU cores efficiently for parallel builds.

2. Step 2: Enable parallel pipelines and increase JVM memory

   Parallel pipelines speed up tasks; more JVM heap memory supports heavier load.

3. Step 3: Evaluate other options

   Lower executors or disabling parallel pipelines reduces performance; build retention affects storage, not speed.

4. Final Answer:

   Set executors to 8, enable parallel pipelines, and increase JVM heap memory -> Option D

5. Quick Check:

   Executors = CPU cores + parallel + memory up = best [OK]

Hint: Match executors to CPU cores and enable parallel pipelines [OK]

Common Mistakes:

• Setting executors too low or too high
• Disabling parallel pipelines unnecessarily
• Confusing build retention with performance tuning