immediately fail whole matrix job if one configuration fails

107 views
Skip to first unread message

Simon Haegler

unread,
Jul 10, 2015, 3:39:44 AM7/10/15
to jenkins...@googlegroups.com
hi group

is there a way to immediately fail a matrix job as soon as one of its configuration fails?
my motivation is to free up slave resources as early as possible...

TIA,
simon

Simon Richter

unread,
Jul 10, 2015, 4:08:07 AM7/10/15
to jenkins...@googlegroups.com
Hi,

On 10.07.2015 09:39, Simon Haegler wrote:

> is there a way to immediately fail a matrix job as soon as one of its
> configuration fails?

The usual way is to define one or more "touchstone configurations" that
are built first, and starting the remaining jobs only if these succeeded.

Simon

signature.asc

Simon Haegler

unread,
Jul 15, 2015, 3:14:26 AM7/15/15
to jenkins...@googlegroups.com
The usual way is to define one or more "touchstone configurations" that
are built first, and starting the remaining jobs only if these succeeded.

thanks for your answer. my first attempt to configure touchstone configurations failed, i.e. it correctly prints "touchstone configs resulted in failure..." at the end but it still ran all configurations?!

11:30:31 Triggering PRT_BC_TEST,PRT_CC_OPT,PRT_TC_VC10,jdk7,win7_32
11:30:31 Triggering PRT_BC_REL,PRT_CC_NOPT_SYM,PRT_TC_VC11,jdk7,win7_64
11:30:31 Triggering PRT_BC_TEST,PRT_CC_OPT,PRT_TC_VC10,jdk7,win7_64
11:30:31 Triggering PRT_BC_REL,PRT_CC_NOPT_SYM,PRT_TC_VC11,jdk7,win7_32
11:30:31 Triggering PRT_BC_TEST,PRT_CC_OPT,PRT_TC_GCC,jdk7,rhel6
11:30:31 Triggering PRT_BC_REL,PRT_CC_NOPT_SYM,PRT_TC_VC10,jdk7,win7_32
... 
19:27:11 Touchstone configurations resulted in FAILURE, so aborting...

do i need to chain two matrix jobs together? this would kind of defeat the "touchstone" option...

TIA,
simon

Simon Richter

unread,
Jul 15, 2015, 2:10:27 PM7/15/15
to jenkins...@googlegroups.com
Hi,

On 15.07.2015 09:14, Simon Haegler wrote:

> thanks for your answer. my first attempt to configure touchstone
> configurations failed, i.e. it correctly prints "touchstone configs
> resulted in failure..." at the end but it still ran all configurations?!

Then the specificiation is probably broken. This is an expression, for
example for one job that has an axis "cpu" with the values "x86" and
"x64", I use

cpu=="x86"

Apparently, your configuration selects all configurations as touchstone.

Simon


signature.asc

Simon Haegler

unread,
Jul 16, 2015, 7:03:46 AM7/16/15
to jenkins...@googlegroups.com
hi,

you nailed it - my filter was wrong.

thanks & best,
simon
Reply all
Reply to author
Forward
0 new messages