![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
jenkins-multijob-plugin |
|
Created:
|
31/Jul/13 8:25 PM
|
|
Description:
|
I have on several occasions seen a multijob mark its overall status as aborted rather than failed after one phase fails. Several of the other phases are marked as aborted, but I suspect they were aborted due to the failure, and either way I'd imagine that a failed status should supersede an aborted status. Furthermore, jenkins does not generate an email notification as the job is not unstable, but rather aborted.
Here's the console output of one such job:
Starting build job MyProj-Trunk-Win32-BuildFreeRelease.
Starting build job MyProj-Trunk-BlackBerry10.
Starting build job MyProj-Trunk-Android.
Starting build job MyProj-Trunk-iOS.
Starting build job MyProj-Trunk-Win32-BuildReleaseAndTest.
Starting build job MyProj-Trunk-Win32-BuildBlueprintsRelease.
Starting build job MyProj-Trunk-Win32-BuildDistribution.
Starting build job MyProj-Trunk-Win32-BuildSteamRelease.
Finished Build : #1006 of Job : MyProj-Trunk-Win32-BuildDistribution with status :SUCCESS
Finished Build : #1007 of Job : MyProj-Trunk-Win32-BuildFreeRelease with status :FAILURE
Build step 'MultiJob Phase' marked build as failure
Finished: ABORTED
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Paul Siegel
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
