Quantcast

[JIRA] (JENKINS-15084) uilds aborted during shutdown are marked as successful (stable) after restart

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15084) uilds aborted during shutdown are marked as successful (stable) after restart

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 08/Sep/12 1:09 PM
Description:

I've repeatedly seen that builds which are aborted during shutdown (sometimes we've to restart Jenkins because of heap problems) are marked as successful, while they IMO should be marked as aborted.
This is causing problems for us because warning trends reported by the Analysis plugins become invalid at that point.

Environment: Jenkins 1.424.3
Project: Jenkins
Priority: Major Major
Reporter: kutzi
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15084) Builds aborted during shutdown are marked as successful (stable) after restart

JIRA noreply@jenkins-ci.org
Change By: kutzi (08/Sep/12 1:10 PM)
Summary: uilds Builds  aborted during shutdown are marked as successful (stable) after restart
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15084) Builds aborted during shutdown are marked as successful (stable) after restart

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: kutzi (08/Sep/12 1:10 PM)
Description: I've repeatedly seen that builds which are aborted during shutdown (sometimes we've to restart Jenkins because of heap problems) are marked as successful  when Jenkins starts up afterwards , while they IMO should be marked as aborted.

This is causing problems for us because warning trends reported by the Analysis plugins become invalid at that point.

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
Loading...