Disk space management in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Disk Usage Plugin: Output Interpretation

You run the Jenkins Disk Usage plugin report on a Jenkins master node. The output shows:

Workspace: 5 GB
Builds: 10 GB
Artifacts: 3 GB
Other: 2 GB

What is the total disk space used by this Jenkins job?

A 20 GB

B 15 GB

C 10 GB

D 5 GB

💡 Hint

Add all the categories shown in the report to find total usage.

The total disk space is the sum of Workspace (5 GB), Builds (10 GB), Artifacts (3 GB), and Other (2 GB), which equals 20 GB.

🔀 Workflow

intermediate

Jenkins Pipeline: Clean Workspace Step Placement

In a Jenkins pipeline, you want to clean the workspace to free disk space before starting a new build. Where should you place the cleanWs() step to ensure the workspace is cleaned at the right time?

A In the middle of the pipeline after compiling but before testing

B At the end of the pipeline after all build steps

C At the very start of the pipeline before any build steps

D Only inside the post section on build failure

💡 Hint

Think about when you want to remove old files to avoid interference.

Cleaning the workspace at the start ensures no leftover files from previous builds affect the current build and frees disk space before building.

❓ Troubleshoot

advanced

Jenkins Disk Space Warning: Cause Identification

A Jenkins master node shows a disk space warning despite regular workspace cleaning. Which of the following is the most likely cause?

A Build artifacts are not being deleted after retention period

B The cleanWs() step is running too early in the pipeline

C The Jenkins master has too many executors configured

D The Jenkins user does not have permission to run builds

💡 Hint

Think about what files remain even after workspace cleaning.

Build artifacts can accumulate if not deleted after their retention period, causing disk space warnings even if workspaces are cleaned.

❓ Configuration

advanced

Configuring Jenkins to Automatically Clean Old Builds

Which configuration snippet in a Jenkins pipeline script will automatically discard builds older than 10 days and keep only the last 5 builds to save disk space?

A properties([buildDiscarder(logRotator(daysToKeep: '10', numToKeep: '5'))])

B properties([buildDiscarder(logRotator(daysToKeepStr: 10, numToKeepStr: 5))])

C properties([buildDiscarder(logRotator(daysToKeepStr: '10', numToKeepStr: '5'))])

D properties([buildDiscarder(logRotator(daysToKeep: 10, numToKeep: 5))])

💡 Hint

Check the parameter types and whether they expect strings or integers.

The correct syntax uses integer values for daysToKeep and numToKeep parameters inside logRotator.

✅ Best Practice

expert

Best Practice for Managing Disk Space on Jenkins Agents

Which of the following is the best practice to manage disk space on Jenkins agents to avoid build failures due to full disks?

A Increase the disk size of agents without cleaning old files

B Schedule regular cleanup jobs that delete old workspaces and unused files on agents

C Disable workspace cleanup to keep all build data for debugging

D Run all builds on the Jenkins master node instead of agents

💡 Hint

Think about sustainable ways to keep disk space free over time.

Regular cleanup jobs on agents prevent disk space from filling up and avoid build failures, which is a sustainable best practice.