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

The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.

    XMLWordPrintable

Details

    Description

      Activating the 'Discard Old Builds' checkbox on a job allows an Advanced option to specify 'Max # of builds to keep with artifacts'.
      This does not seem to clean up the artifacts for my builds anymore.
      I have tested 1.502, 1.503, 1.504 up to 1.510. It works fine in 1.502 but in none of the later versions.

      The artifacts I refer to are archived with the default archiving mechanism (not the archiving that can be configured as a post-step).

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-17355 LogRotator does not delete Maven Artifacts

          • Major - Major loss of function.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-17553 Archived artifacts of Maven Modules are no longer cleaned up

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted"

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 29 older comments
            stephanebruckert Stéphane Bruckert added a comment -

            Same problem than Sergei Ivanov.

            stephanebruckert Stéphane Bruckert added a comment - Same problem than Sergei Ivanov.
            baboulama Thomas VIN added a comment -

            Hello,

            We're running Jenkins 1.533 and we still notice the same behavior reported by Sergei Ivanov.
            Even though we have old builds properly deleted, the clean is not propagated to the underlying modules for which we keep having a bunch of orphans.

            Best regards.

            baboulama Thomas VIN added a comment - Hello, We're running Jenkins 1.533 and we still notice the same behavior reported by Sergei Ivanov. Even though we have old builds properly deleted, the clean is not propagated to the underlying modules for which we keep having a bunch of orphans. Best regards.
            sc_rsc Stefan Cordes added a comment - - edited

            Got an
            Jan 28, 2014 9:03:44 AM hudson.model.Run execute
            SEVERE: Failed to rotate log
            java.io.IOException: e:\jenkins\jobs\<.....>\modules\com.<...>$<....>\builds\2013-10-23_11-57-46 looks to have already been deleted
            {{ at hudson.model.Run.delete(Run.java:1432)}}
            {{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}}
            {{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}}
            {{ at hudson.model.Job.logRotate(Job.java:437)}}
            {{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}}
            {{ at hudson.model.Run.execute(Run.java:1728)}}
            {{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}}
            {{ at hudson.model.ResourceController.execute(ResourceController.java:88)}}
            {{ at hudson.model.Executor.run(Executor.java:246)}}
            with Jenkins ver. 1.532.1.
            (Mentioned directory 2013-10-23_11-57-46 is not existing on file system).

            LogRotator should continue deleting all other matching jobs.

            sc_rsc Stefan Cordes added a comment - - edited Got an Jan 28, 2014 9:03:44 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException: e:\jenkins\jobs\<.....>\modules\com.<...>$<....>\builds\2013-10-23_11-57-46 looks to have already been deleted {{ at hudson.model.Run.delete(Run.java:1432)}} {{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}} {{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}} {{ at hudson.model.Job.logRotate(Job.java:437)}} {{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}} {{ at hudson.model.Run.execute(Run.java:1728)}} {{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:88)}} {{ at hudson.model.Executor.run(Executor.java:246)}} with Jenkins ver. 1.532.1. (Mentioned directory 2013-10-23_11-57-46 is not existing on file system). LogRotator should continue deleting all other matching jobs.
            jglick Jesse Glick added a comment -

            @baboulama, @sc_rsc: the originally reported bug here is fixed; do not reopen.

            jglick Jesse Glick added a comment - @baboulama, @sc_rsc: the originally reported bug here is fixed; do not reopen.
            jglick Jesse Glick added a comment -

            Filed JENKINS-22395 for a problem actually deleted old builds under unknown conditions.

            jglick Jesse Glick added a comment - Filed JENKINS-22395 for a problem actually deleted old builds under unknown conditions.

            People

              Unassigned Unassigned
              pjoran Per J. Lund
              Votes:
              6 Vote for this issue
              Watchers:
              22 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: