The usual way is to define one or more "touchstone configurations" that
are built first, and starting the remaining jobs only if these succeeded.
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