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

Asynchronous cleanup not removing renamed workspace directories on slaves

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: ws-cleanup-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.121.3
      ws-cleanup 0.34
    • Similar Issues:

      Description

      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 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

            Activity

            jbochenski Jakub Bochenski created issue -
            jbochenski Jakub Bochenski made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-27648 [ JENKINS-27648 ]
            jbochenski Jakub Bochenski made changes -
            Environment Jenkins 1.579
            ws-cleanup 0.24
            ws-cleanup 0.34
            jbochenski Jakub Bochenski made changes -
            Environment ws-cleanup 0.34 Jenkins ver. 2.121.3
            ws-cleanup 0.34
            jbochenski Jakub Bochenski made changes -
            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. 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 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.
            jbochenski Jakub Bochenski made changes -
            Link This issue depends on JENKINS-24824 [ JENKINS-24824 ]
            jbochenski Jakub Bochenski made changes -
            Issue Type Bug [ 1 ] Improvement [ 4 ]

              People

              Assignee:
              olivergondza Oliver Gond┼ża
              Reporter:
              jbochenski Jakub Bochenski
              Votes:
              15 Vote for this issue
              Watchers:
              26 Start watching this issue

                Dates

                Created:
                Updated: