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

Archived artifacts of Maven Modules are no longer cleaned up

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Jenkins 1.504

      After upgrading from 1.500 to 1.504 I noticed rapidly declining free diskspace on out build master. Looking into it, I noticed that the settings for Artifact retention (Max # of builds to keep with artifacts) does not work for archived module artifacts anymore, i.e. none maven artifacts are discarded, but maven artifacts are retained as long as the build is retained (in our case increasing the diskspace used by 30GB per day).

      I have not yet looked into it, but it seems to be related to JENKINS-16979.

          [JENKINS-17553] Archived artifacts of Maven Modules are no longer cleaned up

          Same issue here, running 1.506. The script does not make any difference. Due to the number and size of our builds, this really is a problem for us.

          Henrik Horneber added a comment - Same issue here, running 1.506. The script does not make any difference. Due to the number and size of our builds, this really is a problem for us.

          Still broken in 1.509.1 LTS.

          Henrik Horneber added a comment - Still broken in 1.509.1 LTS.

          Jason Klapste added a comment -

          Still broken in 1.519

          Jason Klapste added a comment - Still broken in 1.519

          Seeing this is 1.514 as well.

          Brent Atkinson added a comment - Seeing this is 1.514 as well.

          kutzi added a comment -

          Looks like a duplicate of JENKINS-17508 to me. Has anyone tried 1.515?

          kutzi added a comment - Looks like a duplicate of JENKINS-17508 to me. Has anyone tried 1.515?

          Looks like duplicate of JENKINS-17355 and JENKINS-17508

          After update to 1.515 I was able to reclaim 100GB of artifacts from maven modules.

          I think we can mark this as fixed.

          Geoff Cummings added a comment - Looks like duplicate of JENKINS-17355 and JENKINS-17508 After update to 1.515 I was able to reclaim 100GB of artifacts from maven modules. I think we can mark this as fixed.

          talios added a comment - - edited

          After running low on disk space I just went thru and configured my jobs to discard the old builds, but didn't really see any immediate disk space come back so assume this is a nightly job or something.

          So I decided I would run the script mentioned above to force a quick reclamation of space, but ended up getting:

          java.io.IOException: /build/jenkins/data/jobs/com.smxemail.platform/modules/com.smxemail$com.smxemail.template/builds/2013-08-14_06-02-59 looks to have already been deleted
          	at hudson.model.Run.delete(Run.java:1369)
          	at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:418)
          	at hudson.tasks.LogRotator.perform(LogRotator.java:136)
          	at hudson.model.Job.logRotate(Job.java:437)
          

          I had manually deleted some builds from the server via the GUI and now Jenkins is in a state of confusion.

          I suspect this will also be happening when any normal log rotation job is run - and preventing reclamation.

          talios added a comment - - edited After running low on disk space I just went thru and configured my jobs to discard the old builds, but didn't really see any immediate disk space come back so assume this is a nightly job or something. So I decided I would run the script mentioned above to force a quick reclamation of space, but ended up getting: java.io.IOException: /build/jenkins/data/jobs/com.smxemail.platform/modules/com.smxemail$com.smxemail.template/builds/2013-08-14_06-02-59 looks to have already been deleted at hudson.model.Run.delete(Run.java:1369) at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:418) at hudson.tasks.LogRotator.perform(LogRotator.java:136) at hudson.model.Job.logRotate(Job.java:437) I had manually deleted some builds from the server via the GUI and now Jenkins is in a state of confusion. I suspect this will also be happening when any normal log rotation job is run - and preventing reclamation.

          talios added a comment -

          Discussion in IRC confirms that Jenkins doesn't do this as a nightly process, and should just clean up its own state automatically after a few builds. Hopefully my old builds will start to be removed soon.

          talios added a comment - Discussion in IRC confirms that Jenkins doesn't do this as a nightly process, and should just clean up its own state automatically after a few builds. Hopefully my old builds will start to be removed soon.

          talios added a comment -

          Further - it would seem that my jenkins is now hosed with the above exception. After manually deleting some builds via the GUI, the above exception keeps trying for various builds.

          I've tried working around this by running a mkdir on each directory it complains about, which seems to work momentarily, but then comes back with the exception.

          The directory exists, yet for some reason Run.delete() is getting a false result to the call to isDirectory() and throwing the exception.

          talios added a comment - Further - it would seem that my jenkins is now hosed with the above exception. After manually deleting some builds via the GUI, the above exception keeps trying for various builds. I've tried working around this by running a mkdir on each directory it complains about, which seems to work momentarily, but then comes back with the exception. The directory exists, yet for some reason Run.delete() is getting a false result to the call to isDirectory() and throwing the exception.

          Jesse Glick added a comment -

          @talios: filed JENKINS-22395 for a problem actually deleted old builds under unknown conditions.

          Jesse Glick added a comment - @talios: filed JENKINS-22395 for a problem actually deleted old builds under unknown conditions.

            Unassigned Unassigned
            paux Stephan Pauxberger
            Votes:
            5 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: