This sounds somewhat similar to what I'm doing with a set of jobs. I have a
matrix job that produces 32-bit and 64-bit builds of a piece of software, on a
variety of Linux platforms, in a bunch of configurations. Each of these stores
away the produced binaries as job artifacts.
There is another
Thanks for the feedback, Kevin.
It *is *my intent to run the same steps on each cell in the matrix (sans
things which evaluate to false using the combination filter). The last
step of each applicable configuration should be "get the logs from the
target this the set of tests was run against",
Why not just run this last job as a child job of the matrix build? The matrix
build is really designed for running the *same* steps for each cell in the
matrix; if you find yourself trying to coerce it into handling an entire flow
of builds, you're probably heading the wrong direction.
The purp
Thanks for the quick reply, Sami.
I'm interested in forcing the particular configuration to run last because
I have lots of tests which generate quite a bit of useful debugging info on
the back-end of the target that I am running the exhaustive tests against.
Once the testing is complete, I r
You cannot control the order in which matrix job builds its configurations.
You need to remove the configuration you want to run last and make a new
non-matrix job. Then make the matrix job trigger a build of the non-matrix job.
If this is not good for you, please explain what you are trying to
I have a matrix build with touchstone builds, multiple configurations,
etc. I have a step which should be the *last* step in the matrix (not a
triggered parameterized build, etc) and can't find a way to force the job
to run that last step last.
I've tried using the "Run each configuration seque
