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

Asynchronous cleanup not removing renamed workspace directories on slaves

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • ws-cleanup-plugin
    • None
    • Jenkins 1.579
      ws-cleanup 0.24

    Description

      After upgrading to ws-cleanup 0.24 in order to get the asynchronous cleanup function we noticed the workspaces on our slaves getting renamed to the form of ${WORKSPACE}ws-cleanup${TIMESTAMP}. (ie, job1 would become job1_ws-cleanup_1411197183394). The expected behavior under ws-cleanup 0.24 is that these were temporary to support asynchronous processing and would be deleted. However, these directories never get removed from the slave. Over time, the slave hard drives filled up resulting in build failures.

      Attachments

        Issue Links

          is blocking

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-53579 Asynchronous cleanup not removing renamed workspace directories on slaves

          • Major - Major loss of function.
          • Open
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-27648 Introduce directory disposal service

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

          Activity

            Ascending order - Click to sort in descending order
            View 56 older comments
            dhs Dirk Heinrichs added a comment -

            But the problem still persists (here too, BTW.). So why file a new issue for the VERY SAME problem? Reopening a ticket is common practice in such cases.

            dhs Dirk Heinrichs added a comment - But the problem still persists (here too, BTW.). So why file a new issue for the VERY SAME problem? Reopening a ticket is common practice in such cases.
            broussar Adam Brousseau added a comment -

            We also have this issue but only on Windows slaves (connected through Cygwin SSH).

            broussar Adam Brousseau added a comment - We also have this issue but only on Windows slaves (connected through Cygwin SSH).
            zakharovdi Denis Zakharov added a comment -

            Have the same issue. Jenkins 2.121.1 in docker container(workspace on volume) , ws-cleanup 0.34

            zakharovdi Denis Zakharov added a comment - Have the same issue. Jenkins 2.121.1 in docker container(workspace on volume) , ws-cleanup 0.34
            olivergondza Oliver Gondža added a comment -

            Guys, this ticket was resolved year and a half ago. Please, file a separate issue.

            olivergondza Oliver Gondža added a comment - Guys, this ticket was resolved year and a half ago. Please, file a separate issue.
            jbochenski Jakub Bochenski added a comment -

            Opened https://issues.jenkins-ci.org/browse/JENKINS-53579 now can we get this addressed?

            jbochenski Jakub Bochenski added a comment - Opened https://issues.jenkins-ci.org/browse/JENKINS-53579 now can we get this addressed?

            People

              olivergondza Oliver Gondža
              tmoore Tom Moore
              Votes:
              18 Vote for this issue
              Watchers:
              40 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: