• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: workflow-job-plugin
• Labels:

  • regression
• Environment:

  Centos 7.2.1511 (master and slaves)
  Jenkins 2.176.2
  Jenkins master - open-jdk 1.8.0_212
  Jenkins slaves - Oracle jdk 1.8.0_60
  
  Jenkins running as docker container (standalone)
  Attached plugin versions as file
  
  

1. stuck-build-2.tar.gz

   16 kB

   2019-08-26 21:49

2. 

   failed.PNG

   70 kB

   2019-08-26 21:44

3. 

   Capture2.PNG

   66 kB

   2019-08-26 21:32

4. tdump

   75 kB

   2019-08-26 20:17

5. 

   Capture.PNG

   70 kB

   2019-08-26 20:13

6. 

   image.png

   19 kB

   2019-08-26 14:47

7. plugins.txt

   5 kB

   2019-08-26 12:53

[JENKINS-59083] Builds stuck on "is already in progress" forever

Roy Arnon created issue - 2019-08-26 12:58

Roy Arnon made changes - 2019-08-26 13:00

Link

New: This issue is related to JENKINS-46076 [ JENKINS-46076 ]

Roy Arnon made changes - 2019-08-26 13:02

Description

Original: After upgrading our jenkins master and plugins, some of our build jobs - specifically it seemed like most pipeline jobs - were stuck waiting for previous build to complete, even though it already completed. !https://files.slack.com/files-pri/T0255EC3D-FMP3HKY56/image.png!   This seems to have been caused by JENKINS-46076. After donwngrading the plugin to version 2.32, all build were working correctly.   From some testing, it seems that calling {code:java} Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated() {code} On the previous build (in the sample case build #185) returns true, although the build is completed and the log seems to have been completed. This issue happened immediately after restarting the jenkins instance with any of our pipeline jobs

New: After upgrading our jenkins master and plugins, some of our build jobs - specifically it seemed like most pipeline jobs - were stuck waiting for previous build to complete, even though it already completed. !https://files.slack.com/files-pri/T0255EC3D-FMP3HKY56/image.png!   This seems to have been caused by JENKINS-46076. After donwngrading the plugin to version 2.32, all builds were working correctly.   From some testing, it seems that calling {code:java} Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated() {code} On the previous build (in the sample case build #185) returns true, although the build is completed and the log seems to have been completed. This issue happened immediately after restarting the jenkins instance with any of our pipeline jobs

Roy Arnon made changes - 2019-08-26 14:47

Attachment

New: image.png [ 48421 ]

Roy Arnon made changes - 2019-08-26 20:12

Attachment

New: stuck-build.tar.gz [ 48501 ]

Roy Arnon made changes - 2019-08-26 20:13

Attachment

New: Capture.PNG [ 48502 ]

Roy Arnon made changes - 2019-08-26 20:17

Attachment

New: tdump [ 48503 ]

Roy Arnon made changes - 2019-08-26 21:32

Attachment

New: Capture2.PNG [ 48504 ]

Roy Arnon made changes - 2019-08-26 21:44

Attachment

New: failed.PNG [ 48505 ]

Roy Arnon made changes - 2019-08-26 21:46

Attachment

Original: stuck-build.tar.gz [ 48501 ]

Roy Arnon made changes - 2019-08-26 21:49

Attachment

New: stuck-build-2.tar.gz [ 48506 ]

Load more newer history items