Disk space management in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is disk space management in Jenkins?

Disk space management in Jenkins means keeping track of and cleaning up files and data that Jenkins creates, so the server doesn't run out of storage.

beginner

How can you check disk usage on a Jenkins server?

You can check disk usage by running commands like df -h to see free space or du -sh /var/lib/jenkins to see Jenkins folder size.

intermediate

What Jenkins plugin helps manage disk space by cleaning old builds?

The 'Discard Old Builds' feature or plugin helps remove old builds to free up disk space automatically.

beginner

Why is it important to manage disk space in Jenkins?

If disk space runs out, Jenkins can stop working properly, causing builds to fail and slowing down development.

intermediate

Name a simple way to automatically delete old Jenkins build data.

You can configure 'Build Discarder' settings in Jenkins jobs to keep only a certain number of builds or days, deleting older ones automatically.

Which command shows the free disk space on a Linux server running Jenkins?

A ps aux

B ls -l

C df -h

D cat /etc/passwd

The command df -h displays disk space usage in a human-readable format.

What does the Workspace Cleanup Plugin do in Jenkins?

A Monitors CPU usage

B Deletes old workspace files to free disk space

C Builds new projects automatically

D Manages user permissions

The Workspace Cleanup Plugin removes old files in the workspace to save disk space.

Why should you configure build discarder settings in Jenkins jobs?

A To change build environment variables

B To speed up the build process

C To increase the number of builds stored

D To limit the number of stored builds and save disk space

Build discarder settings help keep only recent builds, preventing disk space from filling up.

What happens if Jenkins runs out of disk space?

A Builds may fail and Jenkins may become unstable

B Jenkins will automatically increase disk space

C Nothing, Jenkins ignores disk space

D Jenkins will delete all jobs

Running out of disk space causes build failures and instability in Jenkins.

Which folder typically contains Jenkins data that can grow large over time?

A /var/lib/jenkins

B /etc/jenkins

C /usr/bin/jenkins

D /home/jenkins

The Jenkins home directory, usually at /var/lib/jenkins, stores build data and configurations.

Explain how you would monitor and manage disk space on a Jenkins server to prevent build failures.

Think about checking space, cleaning old files, and automatic deletion.

Describe why disk space management is critical in Jenkins and what problems it helps avoid.

Consider what happens if disk space is full.

Practice

1. What is the main purpose of managing disk space in Jenkins?

easy

A. To reduce the number of Jenkins plugins installed

B. To increase the number of Jenkins users

C. To speed up the Jenkins UI loading time

D. To keep Jenkins builds running smoothly without storage issues

Solution

1. Step 1: Understand Jenkins build process

   Jenkins stores build files and logs in workspaces which consume disk space.

2. Step 2: Identify the effect of disk space on builds

   If disk space runs out, builds can fail or Jenkins may slow down.

3. Final Answer:

   To keep Jenkins builds running smoothly without storage issues -> Option D

4. Quick Check:

   Disk space management = smooth builds [OK]

Hint: Disk space issues cause build failures, manage to avoid them [OK]

Common Mistakes:

• Thinking disk space affects only UI speed
• Confusing disk space with user management
• Assuming plugins control disk space

2. Which Jenkins pipeline step is used to clean the workspace and free disk space?

easy

A. deleteDir()

B. cleanWs()

C. removeWorkspace()

D. clearDisk()

Solution

1. Step 1: Recall Jenkins pipeline steps for workspace cleanup

   The step cleanWs() is designed to delete all files in the current workspace.

2. Step 2: Verify other options

   deleteDir() deletes the current directory but is less specific; others are not valid Jenkins steps.

3. Final Answer:

   cleanWs() -> Option B

4. Quick Check:

   Workspace cleanup step = cleanWs() [OK]

Hint: Remember cleanWs() cleans workspace files in pipelines [OK]

Common Mistakes:

• Using deleteDir() which deletes current dir but not workspace safely
• Assuming removeWorkspace() or clearDisk() exist
• Confusing cleanWs() with plugin names

3. What will happen if you add cleanWs() at the end of a Jenkins pipeline script?

medium

A. The build will fail due to missing workspace files

B. The workspace files will be backed up automatically

C. The workspace files will be deleted after the build completes

D. Nothing happens; cleanWs() is ignored

Solution

1. Step 1: Understand cleanWs() behavior

   cleanWs() deletes all files in the workspace where the build runs.

2. Step 2: Consider placement at pipeline end

   Placing cleanWs() at the end deletes files after build finishes, freeing disk space.

3. Final Answer:

   The workspace files will be deleted after the build completes -> Option C

4. Quick Check:

   cleanWs() at end = workspace cleaned [OK]

Hint: cleanWs() deletes workspace files after build ends [OK]

Common Mistakes:

• Thinking cleanWs() backs up files
• Assuming it causes build failure
• Believing cleanWs() does nothing

4. You added cleanWs() in your Jenkins pipeline, but disk space is still filling up. What is a likely cause?

medium

A. The Disk Usage Plugin is not installed or configured

B. cleanWs() only deletes files older than 7 days

C. cleanWs() does not delete files if the build fails

D. cleanWs() requires manual confirmation to delete files

Solution

1. Step 1: Understand cleanWs() limitations

   cleanWs() deletes workspace files but does not manage other disk usage like old builds or logs.

2. Step 2: Role of Disk Usage Plugin

   The Disk Usage Plugin helps monitor and automate cleanup beyond workspace, including old builds and artifacts.

3. Final Answer:

   The Disk Usage Plugin is not installed or configured -> Option A

4. Quick Check:

   Disk Usage Plugin needed for full cleanup [OK]

Hint: Use Disk Usage Plugin for full disk cleanup automation [OK]

Common Mistakes:

• Believing cleanWs() deletes all disk files
• Thinking cleanWs() deletes only old files
• Assuming cleanWs() needs manual approval

5. How can you automate disk space cleanup in Jenkins to delete old builds and workspace files regularly?

hard

A. Configure the Disk Usage Plugin and add cleanWs() in pipelines

B. Manually delete workspace files after each build

C. Disable all Jenkins plugins to reduce disk usage

D. Increase disk size instead of cleaning files

Solution

1. Step 1: Use Disk Usage Plugin for monitoring and cleanup

   This plugin tracks disk usage and can be set to delete old builds automatically.

2. Step 2: Use cleanWs() in pipelines for workspace cleanup

   Adding cleanWs() deletes workspace files after builds, freeing space regularly.

3. Final Answer:

   Configure the Disk Usage Plugin and add cleanWs() in pipelines -> Option A

4. Quick Check:

   Plugin + cleanWs() = automated cleanup [OK]

Hint: Combine Disk Usage Plugin with cleanWs() for automation [OK]

Common Mistakes:

• Relying on manual deletion only
• Disabling plugins instead of cleaning
• Ignoring disk size limits