Workspace cleanup in Jenkins - Step-by-Step Execution

Process Flow - Workspace cleanup

Start Build

↓

Build Workspace Created

↓

Build Steps Execute

↓

Workspace Cleanup Triggered?

No→Keep Workspace

Yes↓

Delete Workspace Files

↓

Workspace Clean

↓

Build Ends

The workspace is created for a build, build steps run, then optionally the workspace is cleaned by deleting files before the build ends.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
  post {
    always {
      cleanWs()
    }
  }
}

This Jenkins pipeline runs a build stage and always cleans the workspace after the build finishes.

Process Table

Step	Action	Workspace State	Output
1	Start build	Empty	Build started
2	Create workspace	Workspace folder created	Workspace ready
3	Run build steps	Files created in workspace	Building...
4	Post build: cleanWs() called	Workspace files deleted	Workspace cleaned
5	Build ends	Workspace empty	Build finished

💡 Build ends after workspace cleanup, workspace is empty for next build

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Workspace State	Empty	Created	Files present	Cleaned (empty)	Empty

Key Moments - 2 Insights

Why do we clean the workspace after the build?

Cleaning the workspace removes leftover files from previous builds, preventing conflicts or errors in future builds. See execution_table step 4 where cleanWs() deletes files.

What happens if we skip cleanWs()?

The workspace keeps files from previous builds, which might cause unexpected behavior. In execution_table, skipping step 4 means workspace still has files at build end.

Visual Quiz - 3 Questions

Look at the execution table, what is the workspace state after step 3?

A Empty

B Created but empty

C Files present

D Deleted

💡 Hint

Check the 'Workspace State' column at step 3 in the execution_table

At which step does the workspace get cleaned?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for 'cleanWs() called' in the 'Action' column of execution_table

If cleanWs() is not called, what will be the workspace state at build end?

A Empty

B Files present

C Workspace deleted

D Workspace locked

💡 Hint

Refer to key_moments about skipping cleanWs() and its effect on workspace state

Concept Snapshot

Jenkins workspace cleanup:
- Workspace holds files during build
- Use cleanWs() in post section to delete files
- Keeps builds isolated and clean
- Prevents leftover file issues
- Always clean workspace after build

Full Transcript

In Jenkins, each build runs in a workspace folder where files are created. After the build steps finish, it is important to clean the workspace to remove leftover files. This is done by calling cleanWs() in the post section of the pipeline. The flow starts with an empty workspace, files are created during build, then cleanWs() deletes these files before the build ends. This prevents conflicts in future builds by ensuring a fresh workspace each time.