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

Clean up workspace by default in Jenkins core. Add option to not do this

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      In my Jenkins, the first thing I normally do when I create or edit a job configuration - check if workspace cleanup is enabled. 99% of the jobs must have clean up enabled after the build, else if working with larger tasks that demand disk space, it is inevitably used up and requires either manual clean up or additional automated mechanisms to do that.

       

      I imagine this proposal might be controversial, since a lot existing projects rely on the way things currently work, but I'm still putting this here up for opinions and discussions. In my opinion, having any task perform clean build and being detached from environment is a good idea which makes maintenance a little bit easier, even if we're not concerned with disk space. Guess a better solution for this is containerization, but Jenkins could prod his users towards 'clean' projects by default.

        Attachments

          Activity

          naj_oknetul Jan Lutenko created issue -
          naj_oknetul Jan Lutenko made changes -
          Field Original Value New Value
          Description In my Jenkins, the first thing I normally do when I create or edit a job configuration - check if workspace cleanup is enabled. 99% of the jobs must have clean up enabled after the build, else if working with larger tasks that demand disk space, it is inevitably used up and requires either manual clean up or additional automated mechanisms to do that.

           

          I imagine this proposal might be controversial, since a lot existing projects rely on the way things currently work, but I'm still putting this here up for opinions and discussions. In my opinion, having any task perform clean build and being detached from environment is a good idea which makes maintenance a little bit easier, even if we're not concerned with disk space. Guess a better solution for this is containerization, but Jenkins could support this by default.
          In my Jenkins, the first thing I normally do when I create or edit a job configuration - check if workspace cleanup is enabled. 99% of the jobs must have clean up enabled after the build, else if working with larger tasks that demand disk space, it is inevitably used up and requires either manual clean up or additional automated mechanisms to do that.

           

          I imagine this proposal might be controversial, since a lot existing projects rely on the way things currently work, but I'm still putting this here up for opinions and discussions. In my opinion, having any task perform clean build and being detached from environment is a good idea which makes maintenance a little bit easier, even if we're not concerned with disk space. Guess a better solution for this is containerization, but Jenkins could prod his users towards 'clean' projects by default.
          oleg_nenashev Oleg Nenashev made changes -
          Component/s ws-cleanup-plugin [ 15930 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            naj_oknetul Jan Lutenko
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: