Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53319

Restart after plugin updates not respecting jobs in progress

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: core
    • Labels:
    • Environment:
      up-to-date Jenkins 2.121.3 on Ubuntu-16
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            alt_jmellor John Mellor added a comment - - edited

            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
            GitHub has been notified of this commit’s build result

            ERROR: missing workspace /var/lib/jenkins/workspace/teel-alert-processor_master-BGGUGXUXB6BJYZHP7P65LURLIXLCLTBTC2GMBJEPRV4HZIHOCW4A on sbt1
            Finished: FAILURE
             

            Show
            alt_jmellor John Mellor added a comment - - edited 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 GitHub has been notified of this commit’s build result ERROR: missing workspace /var/lib/jenkins/workspace/teel-alert-processor_master-BGGUGXUXB6BJYZHP7P65LURLIXLCLTBTC2GMBJEPRV4HZIHOCW4A on sbt1 Finished: FAILURE  
            Hide
            danielbeck Daniel Beck added a comment -

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

            Show
            danielbeck Daniel Beck added a comment - 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.)

              People

              • Assignee:
                Unassigned
                Reporter:
                alt_jmellor John Mellor
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: