> > After some searching I came across [1] that tells about an option > > added not so long ago for "Disable automatic artifact archiving", its > > in the Advanced part of the Build section of the Hudson config. > > Excellent find! I'll try it out on some of my builds and investigate if we can > script it. > > > I'm not sure what the implications are for not archiving, does any one > > know more about it? > > You won't get artifact downloads, like: > https://hudson.apache.org/hudson/job/ftpserver-trunk-jdk1.6- > ubuntu/lastSuccessfulBuild/org.apache.ftpserver$ftplet-api/artifact/ > > Not sure if Hudson will try to serve these from the slave instead like it does for > the workspace. Besides that, not sure if there are further changes.
The problem is that you would only get the *latest* artifacts and only if they are available in the workspace. As soon as the next build is running that may cleanup the workspace, they are lost. If the build fails then for some reason, users are not even able to get the last "stable" artifact. For Lucene builds we exactly want to archive the artifacts, so we can point users to the download location where they can get the latest successful builds, if they need to try out a non-released version. Uwe
