Workspace cleanup in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of the Jenkins pipeline step for cleaning workspace?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Clean') {
      steps {
        cleanWs()
      }
    }
  }
}

What does the cleanWs() step do when executed?

Jenkins

cleanWs()

A Lists all files in the workspace without deleting

B Deletes all files and folders in the current workspace directory

C Archives the workspace files to a backup location

D Restores the workspace to the last successful build state

💡 Hint

Think about what 'clean' means in a workspace context.

The cleanWs() step removes all files and folders in the workspace to ensure a fresh start for the build.

❓ Configuration

intermediate

How to configure Jenkins to automatically clean workspace after build?

Which Jenkins job configuration option will automatically clean the workspace after each build finishes?

A Enable 'Clean workspace after build' in Build Environment

B Enable 'Discard old builds' in Build Triggers

C Enable 'Delete workspace when build is done' in Post-build Actions

D Enable 'Delete workspace before build starts' in Build Environment

💡 Hint

Look for an option that cleans workspace after the build finishes.

The 'Clean workspace after build' option in Build Environment ensures the workspace is cleaned automatically after the build completes.

❓ Troubleshoot

advanced

Why does Jenkins fail to clean workspace with 'Access Denied' error?

A Jenkins job fails to clean the workspace and shows an 'Access Denied' error. What is the most likely cause?

A The Jenkins user does not have permission to delete files in the workspace directory

B The workspace directory is already empty

C The Jenkins master is offline

D The job is configured to skip workspace cleanup

💡 Hint

Think about file system permissions.

If Jenkins cannot delete files due to permission issues, it will show 'Access Denied'. The Jenkins user must have delete permissions on the workspace.

🔀 Workflow

advanced

Order the steps to safely clean a Jenkins workspace in a pipeline

Arrange these steps in the correct order to safely clean a Jenkins workspace in a pipeline:

A 1,3,4,2

B 3,1,4,2

C 1,4,2,3

D 3,4,1,2

💡 Hint

Think about preserving data before deleting workspace.

First archive artifacts to save important files, then run the build, then clean workspace, and finally notify the team.

✅ Best Practice

expert

What is the best practice to avoid workspace cleanup issues in Jenkins multi-branch pipelines?

In Jenkins multi-branch pipelines, what is the best practice to avoid workspace cleanup conflicts when multiple branches build concurrently?

A Manually clean workspace only once a month

B Disable workspace cleanup to prevent accidental deletion

C Run all branches on the same workspace to save disk space

D Use separate workspaces per branch by enabling 'Use custom workspace' with branch-specific paths

💡 Hint

Think about isolating builds to prevent conflicts.

Using separate workspaces per branch avoids conflicts and accidental deletion when multiple branches build simultaneously.