David: I pass the CI job's workspace into the downstream job using my build pipeline via the clone workspace plugin. The CI job uses the "Post-build Actions" -"Archive for Clone Workspace SCM". The downstream job uses the cloned workspace as a SCM plugin.
Eric On Friday, June 20, 2014 9:49 AM, David Aldrich <david.aldr...@emea.nec.com> wrote: Hi For our large C++ project, hosted in Subversion, we have a Jenkins job that continuously builds the project on a Linux slave. We also have jobs that periodically run regression tests on it (these tests are long and we don’t want to run them on every commit). Currently, the regression tests build their own local copy of the executable and then run tests using that copy. It would be more efficient to pick-up the latest build from the continuous build. How would I arrange for the regression test jobs to pick up the latest build from the continuous build job? Note that, given that I don’t want the regression tests to run after every build, I guess I can’t specify the regression tests as downstream jobs. Any advice would be appreciated. Best regards David -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
