Copying from other jobs's workspace is, of course, a really bad idea, unless you have some means of controlling when the files in the other job's workspace are changed or deleted. Otherwise you will sooner or later have strange build failures that are difficult to investigate.
-- Sami 2012/6/18 lata <l...@2lini.com>: > oops, sorry, i just discovered we can copy from workspace as well. > > > On Monday, June 18, 2012 8:27:11 PM UTC+5:30, lata wrote: >> >> Alan, I'm trying to use this plugin to copy a tar.gz file from a nightly >> build to a test job workspace. the .tar.gz in the nightly build is not an >> archived artifact, but it's available in the ws, with it's node online. It >> seems like i can't use the copy artifact unless it's archived, is that >> right? or is there a way i can copy any file from another Jenkins job's >> ws, >> without having to archive it. Because i really don't want to archive the >> huge nightly build, making a copy from the node to the master. thank you! >> Maybe that's what Les was looking for, too, copy from the slave and not >> master. >> >> -- >> View this message in context: >> http://jenkins.361315.n4.nabble.com/Copy-Artifact-Plugin-tp1584761p4631891.html >> Sent from the Jenkins users mailing list archive at Nabble.com.
