ld not be a delete button there, but
> you should be able to go to advanced, and uncheck the box for the failure
> trigger.
>
> --
> *From: *"John Dexter"
> *To: *jenkinsci-users@googlegroups.com
> *Sent: *Thursday, May 23, 2013 6:42:51
I have a simple test job with a build-step to run a Windows batch file and
two post-build steps to publish xUnit test results and send emails on
failure.
The email post-build step does not have a delete button but the other two
steps both do, and I want to disable/remove the emailing since it's
an
wrote:
> have two jenkins test jobs? maybe i'm missing something.
>
>
> On Thursday, May 16, 2013 4:44:44 PM UTC+5:30, John Dexter wrote:
>>
>> I use boost.test to do unit testing on a C++ project, which has two
>> build-configurations - each configuration pulls in a
I use boost.test to do unit testing on a C++ project, which has two
build-configurations - each configuration pulls in a different 3rd-party
library and our app wraps these, so we have the same suite of tests to
check both are behaving identically.
This means we end up with app_A.exe and app_B.exe
Searching online, I've found no two identical XSLs and no definitive
reference how to get the results of boost.test to work with xUnit/Jenkins -
some versions seem to want stdout, others stdout+stderr, and every version
I've tried has either failed to process my input XML, or produced output
XML th
