Re: Archived artifacts not appearing in build links
On 21-11-2013 11:24, Nigel Magnay wrote: > Hi - > > We have many jobs that work correctly, but one maven (integration) job > is displaying weird behaviour. > > It runs correctly, it reports 'artifacts being archived'. These appear > in the .jenkins directory in the place I'd expect. However, the > left-hand sidebar reports a build size of '1 MB', and there are no > links to be able to download those modules. As far as I can tell, > there's nothing special with the configuration of this project (it was > likely cloned from a different build). > The archived artifacts can be found under each module. I believe that this can be changed by turning off automatic archiving and do explicit archiving as a build step. Mads. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Archived Artifacts
Domi, I think this is the solution to my problem. I will try this. Thanks! On Tue, Dec 18, 2012 at 1:04 PM, domi wrote: > In the advanced section of your maven build, you can "Disable automatic > artifact archiving" > With the "Create Job Advanced Plugin" you can disable this setting per > default for new jobs: > https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin > /Domi > > On 18.12.2012, at 16:26, Kanstantsin Shautsou > wrote: > > > You use maven style project, it saves build artifacts. If you have > problems with space, decrease history. > > > > On 10.12.2012, at 20:41, Nicky Ramone wrote: > > > >> Hello. > >> > >> I noticed that despite my configuration is defined so that no artifacts > are archived, the artifacts are stored in the disk anyway for all builds. > >> Example: > >> > $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz > >> > >> Is this due to fingerprinting? is there any way to avoid this? > >> > >> Thanks > >> Regards > > > >
Re: Archived Artifacts
Hi Nicky, is the comma set on purpose? dummy,tar.gz <- look between dummy and tar Regards Jan Am Montag, 10. Dezember 2012 18:41:36 UTC+1 schrieb Nicky Ramone: > > Hello. > > I noticed that despite my configuration is defined so that no artifacts > are archived, the artifacts are stored in the disk anyway for all builds. > Example: > > $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz > > Is this due to fingerprinting? is there any way to avoid this? > > Thanks > Regards >
Re: Archived Artifacts
In the advanced section of your maven build, you can "Disable automatic artifact archiving" With the "Create Job Advanced Plugin" you can disable this setting per default for new jobs: https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin /Domi On 18.12.2012, at 16:26, Kanstantsin Shautsou wrote: > You use maven style project, it saves build artifacts. If you have problems > with space, decrease history. > > On 10.12.2012, at 20:41, Nicky Ramone wrote: > >> Hello. >> >> I noticed that despite my configuration is defined so that no artifacts are >> archived, the artifacts are stored in the disk anyway for all builds. >> Example: >> $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz >> >> Is this due to fingerprinting? is there any way to avoid this? >> >> Thanks >> Regards >
Re: Archived Artifacts
You use maven style project, it saves build artifacts. If you have problems with space, decrease history. On 10.12.2012, at 20:41, Nicky Ramone wrote: > Hello. > > I noticed that despite my configuration is defined so that no artifacts are > archived, the artifacts are stored in the disk anyway for all builds. > Example: > $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz > > Is this due to fingerprinting? is there any way to avoid this? > > Thanks > Regards
Re: Archived Artifacts
Did anyone notice the same behavior? On Mon, Dec 10, 2012 at 2:41 PM, Nicky Ramone wrote: > Hello. > > I noticed that despite my configuration is defined so that no artifacts > are archived, the artifacts are stored in the disk anyway for all builds. > Example: > > $JENKINS_HOME/jobs/dummy/modules/com.dummy/builds/2012-07-12_10-24-06/archive/com.dummy/dummy/dummy,tar.gz > > Is this due to fingerprinting? is there any way to avoid this? > > Thanks > Regards >
