Yes, that is the plugin we are talking about. In the job that does the build, you tell Jenkins to 'archive' the artifacts, and you specify what should be archived. The artifacts are copied to the Jenkins master, and stored with the other results of the build job.
Later jobs, on different slaves, or the same one, or even the master, can use the 'Copy Artifacts' plugin to obtain a copy of the archived artifacts; the copy will be made in the job's workspace, and then the scripts/etc. in the job can make use of the artifacts. ----- Original Message ----- From: [email protected] To: [email protected] Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) At: Jun 27 2013 12:49:10 Oh... ok. I thought you were talking about this plugin https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin So the idea is to build on my X machine, copy the artifacts to master and then, everytime I need to run a job it will use those artifacts on the slave? Quinta-feira, 27 de Junho de 2013 17:43:25 UTC+1, Kevin Fleming escreveu: No, the artifacts are copied to the Jenkins master when the job ends, not before it runs (they don't exist before it runs). After they are copied, the slave that ran the job is no longer needed for child jobs to be able to access them. ----- Original Message ----- From: [email protected] To: [email protected] At: Jun 27 2013 12:18:52 That's a good idea, but with this plugin artifacts are always copied before a job runs, which means that my X machine has to be always online... Quinta-feira, 27 de Junho de 2013 16:11:45 UTC+1, Andrew Melo escreveu: On Thu, Jun 27, 2013 at 10:09 AM, Tânia Magalhães <[email protected]> wrote: > I am configuring jenkins to perform tests on our product. > > I have a master and severall slaves. > > Before performing the tests we have to checkout the code and building it. We > do it through python scripts. > Our idea was to do this only on the fastest slave machine and then copy all > the binaries and executable files (...) to the others slaves. > Then we also need to have all the script test files in each slave. > > Question: > How to copy the binaries and executable files (...) after building the code > to the others slaves without having to do it for each one? I mean is there a > way to say "do it for every slave machine"? > > Lets say that the slave where the code is build is named X, that we have > others slaves named A, B and C and that we want to copy a folder named > folder_to_copy. > What I am doing on X is: > xcopy C:\folder_to_copy \\A\c$\folder_to_copy /E /I /Y > xcopy C:\folder_to_copy \\B\c$\folder_to_copy /E /I /Y > xcopy C:\folder_to_copy \\C\c$\folder_to_copy /E /I /Y > > Now, imagine that I have much more slaves. How can I do exactly the same > thing but without the need to write a line for each machine? > > By the way, if during the process some of them failed, can we ensure that > the others end successfully? I would recommend having one job that does the build, then using the using the artifact plugin to have jenkins handle moving the build products to the downstream builds that need your files. best, Andrew > > Thanks! > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- Andrew Melo -- 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]. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
