-
Bug
-
Resolution: Fixed
-
Major
-
Fedora 18 x86_64
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).
- duplicates
-
JENKINS-17355 LogRotator does not delete Maven Artifacts
-
- Resolved
-
- is duplicated by
-
JENKINS-17553 Archived artifacts of Maven Modules are no longer cleaned up
-
- Resolved
-
- is related to
-
JENKINS-22395 Run.delete (from LogRotator) failing with "...looks to have already been deleted"
-
- Resolved
-
Code changed in jenkins
User: redlab
Path:
src/main/java/hudson/maven/MavenModuleSetBuild.java
http://jenkins-ci.org/commit/maven-plugin/62637aad472803c7954bc54120dc4f5121146568
Log:
As this is my first look inside Jenkins codebase I not sure it's correct
but perhaps artifacts for modulebuilds should be deleted just as logs
are deleted. see https://issues.jenkins-ci.org/browse/JENKINS-17508
I did not fully test it yet, all unit tests ran fine, but didn't succeed
to run jobs inside Jenkins, due to classloader issues while running
Jenkins in Jetty, to verify deletion
Originally-Committed-As: d4459d9d0f99b951974f6ab1bedf6a580aad9248