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

removing a job (including multibranch/org folder branches/repos) does not remove the workspace

    XMLWordPrintable

Details

    • 2.0.21

    Description

      Removal of a job leaves the workspace intact.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-60451 "JENKINS-2111" warning gets logged for master with 0 executors

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Fixed but Unreleased
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-34177 Delete workspaces when deleting a job

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-11046 Project deletion does not wipe out project workspaces

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-36264 Deleted builds do not delete workspace

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-40930 WorkspaceCleanupThread doesn't work properly with Pipeline jobs

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-51897 Delete work space when PR closed.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-22240 Workspace folder not renamed/deleted when renaming job

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-60969 @libs pseudo-workspace collision due to branch name truncation

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. JENKINS-26471 Split WorkspaceCleanupThread from core

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-30148 Allocate shorter workspace if it will be too long for reasonable use inside build

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-38706 Workspace directory names mangled in multibranch pipeline

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-54640 Workspace folders are not unique

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-67836 Pipeline: Groovy Plugin [SECURITY-2463] excessive path length

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named.

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link branch-api PR 50

          Web Link branch-api PR 129

          Web Link CloudBees Internal CD-180

          Activity

            Ascending order - Click to sort in descending order
            View 61 older comments
            davida2009 David Aldrich added a comment -

            jglick Thanks for your reply. I'm afraid I'm stuck on this one. I don't understand what the console message means nor where to look in order to fix it. Please will you explain what I need to do?

            davida2009 David Aldrich added a comment - jglick Thanks for your reply. I'm afraid I'm stuck on this one. I don't understand what the console message means nor where to look in order to fix it. Please will you explain what I need to do?
            jglick Jesse Glick added a comment -

            Please ask batmat in JENKINS-21942, who was the last to work on that area.

            jglick Jesse Glick added a comment - Please ask batmat in JENKINS-21942 , who was the last to work on that area.
            alexander_samoylov Alexander Samoylov added a comment -

            I am using Jenkins 2.204.3 and Pipeline Plugin 2.6 and this issue is clearly reproducible for me.
            I delete the job with a "Delete Pipeline" button and I see all these workspaces present on every node:

            • <workspace> itself
            • <workspace>@1,2,3...
            • <workspace>@tmp

            Should I reopen this ticket or wait for the next version of the core or plugin?

            alexander_samoylov Alexander Samoylov added a comment - I am using Jenkins 2.204.3 and Pipeline Plugin 2.6 and this issue is clearly reproducible for me. I delete the job with a "Delete Pipeline" button and I see all these workspaces present on every node: <workspace> itself <workspace>@1,2,3... <workspace>@tmp Should I reopen this ticket or wait for the next version of the core or plugin?
            jglick Jesse Glick added a comment -

            alexander_samoylov neither. You should file a fresh issue with complete, self-contained, explicit steps to reproduce from scratch, and Link to this one. (By the way “Pipeline Plugin 2.6” is meaningless. This is just an aggregator with no code.)

            jglick Jesse Glick added a comment - alexander_samoylov neither. You should file a fresh issue with complete, self-contained, explicit steps to reproduce from scratch, and Link to this one. (By the way “Pipeline Plugin 2.6” is meaningless. This is just an aggregator with no code.)
            p_hampson Paul "TBBle" Hampson added a comment - - edited

            I just came across the warning referring to this ticket, on a Jenkins deployment with no executors on the Jenkins node (which should not happen).

            > JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory

            There are actually two possible sources of this warning in the Branch API Plugin itself, checked on v2.6.2.

            If the message is immediately followed (assuming you have FINE logging visible, otherwise you won't see it) by
            > no available workspace root for hudson.model.Hudson@...

            then it's come from a call to locate, which will happen when a job is deleted or renamed, as the Deleter runs a task on each node (jenkins.getNodes()), which will trigger a call to locate for the Jenkins node, which hits this warning, returns null, and is ignored.

            If no such message followed the warning (and you have FINE logging visible), then it might have come from Collector reacting to the Jenkins node coming online and calling getWorkspaceRoot directly, which will again return null and be ignored.

            This warning means it won't clean up orphaned/renamed workspaces on the Jenkins node, but if you have no executor there, then you shouldn't have any to clean up anyway.

            Edit: I just noticed that JENKINS-60451 was logged for exactly this.

            p_hampson Paul "TBBle" Hampson added a comment - - edited I just came across the warning referring to this ticket, on a Jenkins deployment with no executors on the Jenkins node ( which should not happen ). > JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory There are actually two possible sources of this warning in the Branch API Plugin itself, checked on v2.6.2 . If the message is immediately followed (assuming you have FINE logging visible, otherwise you won't see it) by > no available workspace root for hudson.model.Hudson@... then it's come from a call to locate , which will happen when a job is deleted or renamed, as the Deleter runs a task on each node ( jenkins.getNodes() ), which will trigger a call to locate for the Jenkins node, which hits this warning, returns null , and is ignored. If no such message followed the warning (and you have FINE logging visible), then it might have come from Collector reacting to the Jenkins node coming online and calling getWorkspaceRoot directly, which will again return null and be ignored. This warning means it won't clean up orphaned/renamed workspaces on the Jenkins node, but if you have no executor there, then you shouldn't have any to clean up anyway. Edit: I just noticed that JENKINS-60451 was logged for exactly this.

            People

              jglick Jesse Glick
              bll6969 bll
              Votes:
              90 Vote for this issue
              Watchers:
              100 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: