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 <[email protected]>: > 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. > sles11-x86_64/package-1.1.1-x86_64.rpm > sles12-x86_64/package-1.1.1-x86_64.rpm > centos7-x86_64/package-1.1.1-x86_64.rpm > > > fredag 26. august 2016 19.55.01 UTC+2 skrev Michael Lasevich følgende: >> >> 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 >> you want. >> >> Something like this(untested): >> >> temp="to_archive" >> sh """ >> dir="${temp}/\$(lsb_release -si)-\$(lsb_release -sr)-\$(uname -m)" >> mkdir -p "\${dir}" >> cp *.rpm "${dir}" >> """ >> dir(temp){ archive '**' } >> >> >> -M >> >> On Monday, June 13, 2016 at 1:14:39 AM UTC-7, Sverre Moe wrote: >>> >>> 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/f88d3af3-d8de-47ff-a09c-7ef165dec3a7%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/f88d3af3-d8de-47ff-a09c-7ef165dec3a7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- 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/CAGO7Ob0a3BaOsO_1w006-Jb_7bAeF%2Bzgx3QkzOeszasaVDK9zw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
