Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11046

Project deletion does not wipe out project workspaces

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Duplicate
    • core
    • None
    • Jenkins 1.430 & Red Hat Enterprise Linux Server release 5.5 (Tikanga)

    Description

      When a project is deleted, its directory JENKINS_HOME/jobs/<project> is wiped out. Workspace directories are not deleted if they have been defined outside the project directory (in global system configuration), which has been the default for a while. In multi-node environment, there can be several leftover workspaces (on all slaves where the project has been built).

      There is an easy workaround for this. One can manually delete unwanted leftovers. It would be nice if Jenkins could do proper cleaning, or offer workspace deletion when a project is about to be deleted.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-34781 Cleanup node workspaces on orphan removal

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            danielbeck Daniel Beck added a comment -

            Build record deletion (and even rename for that matter) was resolved by JENKINS-17138.

            danielbeck Daniel Beck added a comment - Build record deletion (and even rename for that matter) was resolved by JENKINS-17138 .
            danielbeck Daniel Beck added a comment -

            Note that in case of offline slaves (common with some configurations) many workspaces still wouldn't be deleted.

            A better solution would be improving the periodic WorkspaceCleanupThread, I think.

            danielbeck Daniel Beck added a comment - Note that in case of offline slaves (common with some configurations) many workspaces still wouldn't be deleted. A better solution would be improving the periodic WorkspaceCleanupThread, I think.
            ahammar Anders Hammar added a comment -

            A project's workspace is still not removed when deleting a project, seen in latest Jenkins as of today (v1.587). This with default setup and no extra plugins, on Windows 7 and JDK 1.6.
            A side effect of this is that if a project is deleted and then a new project is created with the same name, the old workspace is then reused. Very confusing!

            ahammar Anders Hammar added a comment - A project's workspace is still not removed when deleting a project, seen in latest Jenkins as of today (v1.587). This with default setup and no extra plugins, on Windows 7 and JDK 1.6. A side effect of this is that if a project is deleted and then a new project is created with the same name, the old workspace is then reused. Very confusing!
            rtyler R. Tyler Croy added a comment -

            In my opinion this is a pretty big issue for anybody with long-lived agents floating around

            rtyler R. Tyler Croy added a comment - In my opinion this is a pretty big issue for anybody with long-lived agents floating around

            People

              Unassigned Unassigned
              salsa Sami Salonen
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: