Re: Archive multiple artifacts with same name

2016-08-30 Thread David Karlsen
I see the archive DSL have less options (fingerprint) than the wrapper-based version - should they become aligned? 2016-08-29 9:14 GMT+02:00 Sverre Moe : > That worked. > > I removed > step([$class: 'ArtifactArchiver', artifacts: '*.rpm', excludes: null, > fingerprint:

Re: Archive multiple artifacts with same name

2016-08-29 Thread Sverre Moe
That worked. I removed step([$class: 'ArtifactArchiver', artifacts: '*.rpm', excludes: null, fingerprint: true, onlyIfSuccessful: true]) from Build stage. Added archive '**' to the Publish stage. Build Artifacts now list up same named RPMs under a directory for each build slave.

Re: Archive multiple artifacts with same name

2016-08-26 Thread Michael Lasevich
Have you considered creating a temp subdirectory with identity of your OS (can be generated automatically) and then moving your artifacts to that directory and archiving the directory? You end up with artifacts with same names in different directories - easy to browse and link to, and does what

Re: Archive multiple artifacts with same name

2016-08-26 Thread Brian Ray
I can't think of a way around it without naming the artifacts slightly differently. That is frustrating. On Tuesday, August 23, 2016 at 11:39:48 PM UTC-7, Sverre Moe wrote: > > Yes, I am using several stash with different name derived from the slave > name. This helps me to transfer the

Re: Archive multiple artifacts with same name

2016-08-24 Thread Sverre Moe
Yes, I am using several stash with different name derived from the slave name. This helps me to transfer the artifacts to our repository. However my problem is with the archive step that makes the artifacts listed up in Jenkins. In project branch job: Last Successful Artifacts In each project

Re: Archive multiple artifacts with same name

2016-08-23 Thread Brian Ray
Have you looked at the stash step ? You can set an arbitrary name, which is how I got around a similar issue. The only downside is that the artifacts aren't saved with

Re: Archive multiple artifacts with same name

2016-08-12 Thread Sverre Moe
As it stands, using archive is useless unless it can be organized by the node it was built on. Building a single project on multiple linux distributions will produce the same named file, but not necessary the same. mandag 13. juni 2016 10.14.39 UTC+2 skrev Sverre Moe følgende: > > As I am

Archive multiple artifacts with same name

2016-06-13 Thread Sverre Moe
As I am building on multiple slave nodes I get RPM artifacts from each node. Building on 4 64bit Linux OS, I will get 4 distinct artifacts with the same name. Using ArtifactArchiver will only archive one of those distinct archives and overwrite the previous archived artifact. Considering since