After some fumbling around, I found what was actually an incredibly simple
solution. No groovy or anything. I thought I'd reply to myself, in case
some future googler happens across this thread.
- kickoff job is a freestyle job with just one build action,
a "Trigger/call builds on other projects"
On Mon, Oct 1, 2012 at 3:15 PM, Baptiste MATHUS wrote:
> I won't comment much on the smell of having tests that you wanna ignore
> even in CI...
>
It's not extremely pretty, but to clarify, these tests are all passing and
not-ignored in the mainline code. It's just with this new, unfinished
swit
Hi,
I won't comment much on the smell of having tests that you wanna ignore
even in CI...
Even though, what you explain seems quite complicated just to ignore tests
failures.
Did you consider just using Maven Surefire testFailureIgnore parameter?
http://maven.apache.org/plugins/maven-surefire-plu
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:
1
