[JIRA] (JENKINS-53319) Restart after plugin updates not respecting jobs in progress
Title: Message Title Daniel Beck closed an issue as Not A Defect Pipelines are designed to recover after a restart and do not block Jenkins from restarting. There may be a functional bug here, but it's not in core. (We may need to update some core UI labels since this feature was introduced, but that's the full extent of what needs fixing in core.) Jenkins / JENKINS-53319 Restart after plugin updates not respecting jobs in progress Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53319) Restart after plugin updates not respecting jobs in progress
Title: Message Title John Mellor edited a comment on JENKINS-53319 Re: Restart after plugin updates not respecting jobs in progress Excerpt from a failed build log, showing inability to complete:{quote}[info] Compiling 2 Scala sources to /var/lib/jenkins/workspace/teel-alert-processor_master-BGGUGXUXB6BJYZHP7P65LURLIXLCLTBTC2GMBJEPRV4HZIHOCW4A/processor/target/scala-2.12/test-classes ...Resuming build at Wed Aug 29 08:29:31 EDT 2018 after Jenkins restartWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: ???Cannot contact sbt1: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on sbt1 failed. The channel is closing down or has closed downWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineWaiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offlineReady to run at Wed Aug 29 08:38:05 EDT 2018[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipeline GitHub has been notified of this commit’s build resultERROR: missing workspace /var/lib/jenkins/workspace/teel-alert-processor_master-BGGUGXUXB6BJYZHP7P65LURLIXLCLTBTC2GMBJEPRV4HZIHOCW4A on sbt1Finished: FAILURE {quote} Add Comment
[JIRA] (JENKINS-53319) Restart after plugin updates not respecting jobs in progress
Title: Message Title John Mellor commented on JENKINS-53319 Re: Restart after plugin updates not respecting jobs in progress Excerpt from a failed build log, showing inability to complete: [info] Compiling 2 Scala sources to /var/lib/jenkins/workspace/teel-alert-processor_master-BGGUGXUXB6BJYZHP7P65LURLIXLCLTBTC2GMBJEPRV4HZIHOCW4A/processor/target/scala-2.12/test-classes ... Resuming build at Wed Aug 29 08:29:31 EDT 2018 after Jenkins restart Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: ??? Cannot contact sbt1: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on sbt1 failed. The channel is closing down or has closed down Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Waiting to resume part of Advanced Threat Analytics » bluesteel-alert-processor » master #34: sbt1 is offline Ready to run at Wed Aug 29 08:38:05 EDT 2018 [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Add Comment
[JIRA] (JENKINS-53319) Restart after plugin updates not respecting jobs in progress
Title: Message Title John Mellor created an issue Jenkins / JENKINS-53319 Restart after plugin updates not respecting jobs in progress Issue Type: Bug Assignee: Unassigned Attachments: yyy Components: core Created: 2018-08-29 12:48 Environment: up-to-date Jenkins 2.121.3 on Ubuntu-16 Labels: regression Priority: Major Reporter: John Mellor A normal restart after plugin updates is not respecting pipeline jobs in progress. Example pipeline attached. This job aborted in the middle of the "Build and test" stage. Add Comment