either you have have simplified you're setup too much or it would still be then same artifacts from the build no matter what part of the matrix that passes and kicks of the valgrind build. so you should just choose the build project in the copy artifact section of your valgrind project Den 27/11/2012 10.25 skrev "Chris Withers" <ch...@simplistix.co.uk>:
> 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 >
