Disk space management in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to disable deferred wipeout in the Jenkins workspace cleanup step.

Jenkins

steps {
  cleanWs(disableDeferredWipeout: [1])
}

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

AdisableDeferredWipeout()

BdisableDeferredWipeout

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

disableDeferredWipeout() or disableDeferredWipeout without ': true' causes a syntax error.

Using false keeps the default deferred wipeout behavior.

The cleanWs step accepts disableDeferredWipeout: true to disable deferred deletion. Use the boolean true after the colon.

2fill in blank

medium

Complete the code to delete old builds after 10 days.

Jenkins

properties {
  buildDiscarder(logRotator([1]: 10))
}

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

AdaysToKeep

BdaysToKeepStr

CnumToKeep

DartifactDaysToKeep

Attempts:

3 left

💡 Hint

Common Mistakes

Using daysToKeepStr instead of daysToKeep causes type errors.

Using numToKeep controls number of builds, not days.

The logRotator step uses daysToKeep to specify how many days to keep builds before deleting.

3fill in blank

hard

Fix the error in the code to archive artifacts only if they exist.

Jenkins

post {
  always {
    archiveArtifacts artifacts: '[1]', allowEmptyArchive: true
  }
}

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

A**/*.jar

B**/*.txt

C**/*.xml

D**/*.log

Attempts:

3 left

💡 Hint

Common Mistakes

Using a pattern that does not match existing files causes no artifacts archived.

Not setting allowEmptyArchive to true causes build failure if no files found.

Using '**/*.log' archives all log files and allowEmptyArchive: true prevents errors if none exist.

4fill in blank

hard

Fill both blanks to configure disk usage cleanup with days and number of builds.

Jenkins

properties {
  buildDiscarder(logRotator([1]: 7, [2]: 5))
}

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

AdaysToKeep

BnumToKeep

CartifactNumToKeep

DartifactDaysToKeep

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing artifactDaysToKeep with numToKeep causes unexpected behavior.

Using artifactNumToKeep instead of numToKeep affects artifacts, not builds.

daysToKeep sets how many days to keep builds; numToKeep sets how many builds to keep.

5fill in blank

hard

Fill all three blanks to archive only jar files, keep 3 builds, and keep artifacts for 14 days.

Jenkins

properties {
  buildDiscarder(logRotator([1]: 3, [2]: 14))
}

post {
  success {
    archiveArtifacts artifacts: '[3]'
  }
}

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

AnumToKeep

BartifactDaysToKeep

C**/*.jar

DdaysToKeep

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing daysToKeep with artifactDaysToKeep.

Using wrong artifact pattern causes no files archived.

numToKeep limits builds kept; artifactDaysToKeep limits artifact retention days; '**/*.jar' archives jar files.

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