Re: getting JUnit failures to *not* mark build as unstable

2012-10-02 Thread Yuval Shavit
know its number; the downstream build does know the upstream build's number. In other words, the kickoff job doesn't know which mian build it triggered, but the main builds do know what kickoff jobs they came from. But that's not a huge deal for me. On Mon, Oct 1, 2012 at 4:44 PM, Yuval Shavit ysha

getting JUnit failures to *not* mark build as unstable

2012-10-01 Thread Yuval Shavit
Hi all. I have a job with a maven run in which I expect test failures, and I want the job to *not* be marked as UNSTABLE if there are failures; I'll be doing some custom analysis in script tasks after the maven task in which I'll determine the build's status. In other words, what I'd like is:

Re: getting JUnit failures to *not* mark build as unstable

2012-10-01 Thread Yuval Shavit
Yuval Shavit ysha...@akiban.com Hi all. I have a job with a maven run in which I expect test failures, and I want the job to *not* be marked as UNSTABLE if there are failures; I'll be doing some custom analysis in script tasks after the maven task in which I'll determine the build's status