Status: Closed (View Workflow)
Platform: All, OS: Linux
My Maven2 projects are not being made unstable even though the project description
page says there are test failures. The project is set to use a local maven
repository. Hudson version is 1.318
- is duplicated by
JENKINS-4188 Maven2 Job has test Failures but reports the job as a success
This is still happening in hudson 1.319. From conversation on IRC with
"ok, I worked it out, nothing to do with findbugs... it has to do with multiple
Maven goals and Hudson only paying attention to the results of the last one"
"you had mvn -U clean deploy (test runs before deploy) and assuming deploy was
successful, hudson 1.318 will report a blue/green ball even if tests failed"
"I have mvn clean test findbugs:findbugs and since the findbugs part is
successful, hudson reports a blue/green ball even though I had test failures"
"hudson 1.317 reports a yellow (unstable) ball with test failures and findbugs
while hudson 1.318 reports a blue ball with test failures and findbugs being
Interestingly, I did not get this error when running Hudson 1.317 but with the
1.318 Maven plugin - so it looks like it may be a change in Hudson core from
1.317->1.318 that's the culprit.
Code changed in hudson
User: : abayer
[FIXED JENKINS-4177] getResult() is null by default again - no actual live code depended on it being set, as it turned out. Also added integration test for this use case.
Regrettably, I got this fix in about two hours too late to make it into 1.320,
but it'll be in 1.321.
Created an attachment (id=823)
Screenshot of project description page