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.

Practice

1. What is the main purpose of workspace cleanup in Jenkins?

easy

A. To increase the number of concurrent builds

B. To remove old files and keep the build environment clean

C. To backup build artifacts automatically

D. To speed up the Jenkins server startup

Solution

1. Step 1: Understand workspace cleanup concept

   Workspace cleanup removes files from previous builds to avoid clutter and errors.

2. Step 2: Identify the main benefit

   Removing old files keeps the build environment clean and prevents conflicts or disk space issues.

3. Final Answer:

   To remove old files and keep the build environment clean -> Option B

4. Quick Check:

   Workspace cleanup = remove old files [OK]

Hint: Workspace cleanup deletes old build files to keep space free [OK]

Common Mistakes:

• Thinking it speeds up Jenkins server startup
• Confusing cleanup with backup
• Assuming it increases build concurrency

2. Which of the following is the correct syntax to clean the workspace in a Jenkins Pipeline script?

easy

A. cleanWs()

B. cleanWorkspace()

C. deleteWorkspace()

D. removeWs()

Solution

1. Step 1: Recall Jenkins Pipeline workspace cleanup function

   The correct function to clean workspace is cleanWs().

2. Step 2: Verify syntax correctness

   Other options are not valid Jenkins Pipeline steps for workspace cleanup.

3. Final Answer:

   cleanWs() -> Option A

4. Quick Check:

   Jenkins workspace cleanup function = cleanWs() [OK]

Hint: Remember exact function name: cleanWs() [OK]

Common Mistakes:

• Using incorrect function names like cleanWorkspace()
• Adding parentheses incorrectly or missing them
• Confusing with other cleanup commands

3. What will be the output or effect of this Jenkins Pipeline snippet?

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

medium

A. Fails with a syntax error due to missing parameters

B. Prints the workspace contents without deleting anything

C. Archives the workspace files for later use

D. Deletes all files in the current workspace before the build

Solution

1. Step 1: Analyze the cleanWs() step in the pipeline

   The cleanWs() step deletes all files in the current workspace.

2. Step 2: Understand the pipeline effect

   Since it is in the 'Clean' stage, it removes workspace files before further build steps.

3. Final Answer:

   Deletes all files in the current workspace before the build -> Option D

4. Quick Check:

   cleanWs() deletes workspace files [OK]

Hint: cleanWs() deletes workspace files, no parameters needed [OK]

Common Mistakes:

• Thinking cleanWs() only lists files
• Assuming cleanWs() needs parameters
• Confusing cleanWs() with archiving

4. You added cleanWs() in your Jenkins Pipeline, but the workspace is not cleaned. What is a likely cause?

medium

A. cleanWs() only cleans after the build, not before

B. cleanWs() requires additional parameters to work

C. The pipeline is running on a shared agent and workspace cleanup is disabled

D. The Jenkins server needs a restart to apply cleanWs()

Solution

1. Step 1: Understand workspace cleanup behavior on shared agents

   On shared agents, workspace cleanup may be disabled or restricted to avoid deleting others' files.

2. Step 2: Check common misunderstandings about cleanWs()

   cleanWs() works without parameters and cleans immediately; server restart is not needed.

3. Final Answer:

   The pipeline is running on a shared agent and workspace cleanup is disabled -> Option C

4. Quick Check:

   Shared agent restrictions block cleanWs() [OK]

Hint: Check agent type; shared agents may block cleanup [OK]

Common Mistakes:

• Thinking cleanWs() needs parameters
• Assuming cleanup only happens after build
• Restarting Jenkins unnecessarily

5. You want to ensure your Jenkins Pipeline cleans the workspace only after a successful build to save disk space but keep files if the build fails. How can you achieve this?

hard

A. Use post { success { cleanWs() } } block in the pipeline

B. Call cleanWs() at the start of the pipeline

C. Add cleanWs() inside the always post block

D. Configure Jenkins global settings to clean workspace on failure

Solution

1. Step 1: Understand Jenkins post-build actions

   The post block allows running steps based on build result, like success.

2. Step 2: Use conditional cleanup after successful build

   Placing cleanWs() inside post { success { ... } } cleans workspace only if build succeeds.

3. Final Answer:

   Use post { success { cleanWs() } } block in the pipeline -> Option A

4. Quick Check:

   Post success block cleans workspace conditionally [OK]

Hint: Use post { success { cleanWs() } } to clean only on success [OK]

Common Mistakes:

• Cleaning workspace at start loses files before build
• Using always block cleans even on failure
• Expecting global settings to handle conditional cleanup