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

Automatic workspace cleanup issues after upgrade to 0.13

    XMLWordPrintable

Details

    Description

      After upgrading the ws-cleanup plugin to 0.13 all my test projects are not cleaning up their workspaces anymore. There was no special flag set, just the default Cleanup workspace as a post build action. This led to a full hard disk over the weekend on our Jenkins server.:-/

      OK, now I can see that there are some new flags added which I can use to actively set when the workspace should be cleaned. But this is very tedious to set if you had configured the cleanup-ws plugin for more than 50 projects and if you are now forced to edit all these projects by hand. I would suggest these flags to be true per default.

      The next thing: when I tick all fields for "Clean when status is" in my browser's job configuration window and save the job config, the configuration is written into the XML of the job, but when reconfiguring the job I do not see these ticks?!? Running the job deletes the workspace now successfully.

      So my complaints are:

      • I would like to have true as a default for all the "Clean when status is" ticks like it was before
      • Viewing the configuration seems to be broken although the job config XML file is ok

      Attachments

        Activity

          vjuranek vjuranek added a comment -

          Second issue (configuration page vs XML incompatibility) is fixed by pull #8 [1], now working on fixing broken backward compatibility

          [1] https://github.com/jenkinsci/ws-cleanup-plugin/pull/8

          vjuranek vjuranek added a comment - Second issue (configuration page vs XML incompatibility) is fixed by pull #8 [1] , now working on fixing broken backward compatibility [1] https://github.com/jenkinsci/ws-cleanup-plugin/pull/8

          Code changed in jenkins
          User: Vojtech Juranek
          Path:
          src/main/resources/hudson/plugins/ws_cleanup/WsCleanup/config.jelly
          http://jenkins-ci.org/commit/ws-cleanup-plugin/d04af16ba249fba213d1d136eaaea3529478afd3
          Log:
          [FIXED JENKINS-17930] By default do the cleanup regardless on the job result

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vojtech Juranek Path: src/main/resources/hudson/plugins/ws_cleanup/WsCleanup/config.jelly http://jenkins-ci.org/commit/ws-cleanup-plugin/d04af16ba249fba213d1d136eaaea3529478afd3 Log: [FIXED JENKINS-17930] By default do the cleanup regardless on the job result

          Code changed in jenkins
          User: Vojtech Juranek
          Path:
          src/main/java/hudson/plugins/ws_cleanup/WsCleanup.java
          http://jenkins-ci.org/commit/ws-cleanup-plugin/3c63e756add0665f2c7964c4fc5dc91f64dc7558
          Log:
          [FIXED JENKINS-17930, JENKINS-17940] Fix backward compatibility

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/ws_cleanup/WsCleanup.java http://jenkins-ci.org/commit/ws-cleanup-plugin/3c63e756add0665f2c7964c4fc5dc91f64dc7558 Log: [FIXED JENKINS-17930, JENKINS-17940] Fix backward compatibility
          vjuranek vjuranek added a comment -

          Should be fixed in ws-cleanup 0.14 (thanks for reporting and sorry that I didn't spot it before releasing 0.13)

          vjuranek vjuranek added a comment - Should be fixed in ws-cleanup 0.14 (thanks for reporting and sorry that I didn't spot it before releasing 0.13)
          bruce Dirk Kuypers added a comment -

          Thanks for the fix fix.

          I now had the opportunity to restart my server and I can confirm that the UI stuff and defaulting when upgrading is working now.

          bruce Dirk Kuypers added a comment - Thanks for the fix fix. I now had the opportunity to restart my server and I can confirm that the UI stuff and defaulting when upgrading is working now.

          People

            vjuranek vjuranek
            bruce Dirk Kuypers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: