In a matrix build, the following warning is printed, if you don't opt for
"Always Force Sync", or "Clean Workspace":
"This is a matrix build; It is HIGHLY recommended that you enable the 'Always
Force Sync' or 'Clean Workspace' options. Failing to do so will likely result
in child builds not be
tion failed". That's one unforgiving
and unhelpful parser!
On Wednesday, October 31, 2012 10:53:10 PM UTC-5, Jonathan Rice wrote:
>
> I can't get even a supposedly simple JUnit test working on my OS X Jenkins
> system. Can anyone give any advice? I have a test script which
I can't get even a supposedly simple JUnit test working on my OS X Jenkins
system. Can anyone give any advice? I have a test script which just prints the
following dummy JUnit XML text to $(WORKSPACE)/dummy_junit.xml:
Running on eit
I just started a thread ("Tests which require an initial reboot?") which
has a potential use case for successive jobs on the same slave. I need to
test driver builds which require an initial install and reboot, and then
functional tests. One possible way to implement this would be to schedule
c
I'm doing a project which involves building and testing drivers on OS X.
Testing would happen on dedicated slave machines, but the snag is that
after installing the drivers, the machine must be rebooted before
functional testing is started. I can think of two general ways to approach
this in Je
