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, "v
These artifacts are huge, I don't really want to store copies in the
test-project job, I just want to make sure the test-project and
valgring-project jobs use the same artifact...
How do I do that?
Chris
On 27/11/2012 10:28, jes Struck wrote:
either you have have simplified you're setup too
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/2
you can just re copy the artifacts from the build job instead of the test
job
Den 27/11/2012 10.25 skrev "Chris Withers" :
> 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
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
