Have you looked at the stash step <https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-stash-code-stash-some-files-to-be-used-later-in-the-build>? 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 the build. If you need that capability there may be a way to hack that however. On Thursday, August 11, 2016 at 11:15:31 PM UTC-7, Sverre Moe wrote: > > 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 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 each OS may have different versions of libraries one single artifact >> may not work on all the OS. >> >> Is there a way around this problem that will allow me to archive 4 >> artifacts with same name? >> I am using Jenkins Pipeline and performing the following step >> step([$class: 'ArtifactArchiver', artifacts: '*.rpm', excludes: null, >> fingerprint: true, onlyIfSuccessful: true]) >> >> When I was previously using Multi-configuration builds, this was not a >> problem since each configuration would show their own artifacts. >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bcb9d384-ae99-4224-a093-8e0cf142550b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
