"mark" and reference artifacts of another build of a job

[sl...@dresearch-fe.de]

We're looking for a solution for the following scenario.

One build should be marked e.g. by a manual build parameter. And a later build should have access to the artifacts of the marked build.

Until now we've realizied this by filesystem symlinks pointing to the marked builds created as a build step. But it seems that symlinks into the archive area of another build are no longer allowed.

Any suggestions?

Regards,
Steffen

[Richard Bywater]

Have you looked at  https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin already?  That should do roughly what you want although you might need to calculate the build number potentially (possibly using EnvInject plugin? )

Richard

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d057f456-ccdf-4e98-9e1b-6a47f6843602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sl...@dresearch-fe.de]

In general this plugin can do the work. But it creates real copies in our case (and we talk about a big amount of data) because workspace and build archive reside on different partitions. :(

I'm looking more for something like these "lastSuccessfulBuild" links. But it should be possible to customize name, creation, and update of such a link. And it should be accessible using the browser.

[sl...@dresearch-fe.de]

Ping!

Other ideas?