[JIRA] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Jesse Glick started work on JENKINS-33721 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Jesse Glick assigned an issue to Andrew Bayer Jenkins / JENKINS-33721 Hard kill links could be in the build sidepanel Change By: Jesse Glick Assignee: Jesse Glick Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Andrew Bayer commented on JENKINS-33721 Re: Hard kill links could be in the build sidepanel Preliminary PR up at https://github.com/jenkinsci/workflow-job-plugin/pull/4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Andrew Bayer commented on JENKINS-33721 Re: Hard kill links could be in the build sidepanel Thinking about this some... So as best as I can tell, doStop() results in a one-off executor getting used and then interrupted, which I assume leads to the interrupt(boolean forShutdown) method of the AsynchronousExecution getting called, and that prints the "Click here to forcibly terminate running steps" link in the console (and clicking that calls doTerm(), which tries to terminate any FlowNode running and prints the "Click here to forcibly kill entire build" link, and clicking that results in everything getting killed). Is it viable to track that process, i.e., have a transient variable marking whether doStop() has been called, whether doTerm() has been called, and whether doKill() has been called, and then have a transient action that renders the appropriate link in the side panel depending on state? i.e., isBuilding() needs to be true to have any link show up there, if doStop() hasn't been called, the link says "Abort the build" and calls doStop(), if doStop() has been called but doTerm() has not, the link says "Forcibly terminate running steps" and calls doTerm(), and if doTerm() has been called but doKill() has not, the link says "Forcibly kill entire build" and calls doKill(). Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33721) Hard kill links could be in the build sidepanel
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-33721 Hard kill links could be in the build sidepanel Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/22 9:28 AM Labels: robustness Priority: Major Reporter: Emilio Escobar If you have a pipeline job that logged excessively (due to running a mvn -X step inside it) is so difficult to find "term" or "kill" links after the build number and eventually it disappeared. Would be great to have these as more apparent actions in the ui. Could be actions in the build sidepanel (available only when the console links are printed). Add Comment
