Indeed, I use this feature intensively. In my matrix job (Build job), I have: - Days to keep builds : 60 - Max # of builds to keep : 2 - Max # of builds to keep : 40 - Max # of builds to keep with artifacts : 1
The job it seft keeps correctly only 2 jobs, but the oldest still has its artifacts. However, if I go in one of the configuration, I can see it keep ALL the build (like if the "discard old build" was not applied to the configurations ! That is for me an important issue since it can fufill my hard drive in one or two week of builds! I have to manually goes into the forementionned path ( ~/jenkins/jobs/MyJobName/configurations/axis-FOO/foo/axis-BAR/bar/builds) and remove the files manually. I also have a test job which is not matrix bu where I also use the "Discard old build" feature: - Days to keep builds : 60 - number of build to keep 10 (but actually there is more than 10 build kept, so there is also an issue here) - Days to keep artifacts : 60 - Max # of builds to keep with artifacts : 1 (but every build has its artifact kept, so there is also an issue !) Any idea? Thanks a lot for your support ----- Gaetan 2012/4/20 Benjamin Lau <benjamin.a....@gmail.com> > Do you not have the "Discard Old Builds" option configured in your > job? You might want to set that. You can tell it to keep jobs for a > certain number of days... or to keep a certain number of builds. > > Ben > > On Fri, Apr 20, 2012 at 1:35 AM, Gaetan <gae...@xeberon.net> wrote: > > Hi > > > > I really would like to warn again on this issue. > > My matrix build seems not to clean automatically the artifacts of the > > configurations, so this will lead (again) into fulfill my storage. Can > > anyone confirm on it or if I should open a new ticket? > > I think this is a major issue. > > > > ----- > > Gaetan > > > > > > > > > > > > 2012/4/18 Gaetan <gae...@xeberon.net> > >> > >> Hello > >> > >> I have seen a strange behavior on my matrix job: > >> - the master job is correctly cleaned, for instance, after a month if > >> configured so, the artifacts are dropped and the build are correctly > deleted > >> - however this is not the case for the axis jobs, if i go into the page > of > >> one I can see a very long list of build not having been correctly > deleted > >> (not synchronized with the master). I'm not taking about master/slave > >> machine, but the "builds" directory in: > >> > >> ~/jenkins/jobs/MyJobName/configurations/axis-FOO/foo/axis-BAR/bar/builds > >> not beeing synchronised with > >> ~/jenkins/jobs/MyJobName/builds/ > >> > >> Since each build takes 400 Mo on a 2 axis builds (4 configurations), we > >> quickly run out of disk space ! > >> > >> > >> Also, sometimes I cannot remove a given build (it says it cannot be > >> removed because another one is "kept"). It is linked? > >> Thanks a lot. > >> ----- > >> Gaetan > >> > >> > > >
