Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
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
-
-
workflow-job 2.35, workflow-cps 2.74
Description
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.
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
Jenkins.instance.getItemByFullName(...).getBuildByNumber(..).isLogUpdated()
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
Attachments
Issue Links
- causes
-
JENKINS-61604 Pipeline deadlock caused by fix for JENKINS-59083
-
- Resolved
-
- is duplicated by
-
JENKINS-56947 File handle leak in EnvActionImpl when accessing environment of completed builds
-
- Closed
-
- is related to
-
JENKINS-46076 Test flake in CpsThreadTest.stop
-
- Resolved
-
- relates to
-
JENKINS-59328 job hangs although failed after ConcurrentModificationException of ExwsAllocateActionImpl
-
- Open
-
- links to
Yes, I do see a stack trace like that in the log: