We do something similar with our build/test jobs. We do it by passing the build number of "build-project" (and possibly the job name if multiple builds feed to the same test jobs) to "test-project". In turn, "test-project" would pass that same build number to "valgrind-project". That way, "valgrind-project" can use the build number plus the name of the build with the Copy Artifact plugin to get a copy of the same archived files.
On Tuesday, November 27, 2012 1:25:45 AM UTC-8, Chris Withers wrote: > > Hi All, > > I have a job layout roughly like this: > > build-project > | > V > test-project (matrix job) > | > V > valgrind-project > > Now, the artifacts are built by the build job, and they're quite large. > If all configs in the test-project pass, I want valgrind-project to run > against the same artifact that passed the test-project job. > > The way I've done this in the past is to have the test-project job > re-archive the artifacts and then kick off the valgrind-projects, however: > > - that's very space inefficient, as both build-project and > valgrind-project end up storing copies of the artifacts > > - as test-project is a matrix job, it's tricky to figure out which build > artifact the valgrind-project build should use. > > How can I get the valgrind-project kicked off by a successful > test-project run, but use the artifacts from build-project that caused > the test-project job to pass? > > cheers, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk >
