[JIRA] (JENKINS-60051) A blocked Project still occupies an Executor

3 views
Skip to first unread message

mi+jenkins-2019@aldan.algebra.com (JIRA)

unread,
Nov 4, 2019, 8:10:03 PM11/4/19
to jenkinsc...@googlegroups.com
Mikhail T created an issue
 
Jenkins / Bug JENKINS-60051
A blocked Project still occupies an Executor
Issue Type: Bug Bug
Assignee: Unassigned
Components: core, parameterized-trigger-plugin
Created: 2019-11-05 01:09
Priority: Minor Minor
Reporter: Mikhail T

I've created a job, that builds the same sources into 32- or 64-bit binaries depending on the build parameter. The name of the job is "Compile".

I then created two convenience wrapper-projects, one for each architecture: "Compile-64" and "Compile-32".

The wrapper-projects do nothing other than trigger a build of compile with the correct parameter (using the Parametrized Parameter Plugin as suggested here). The checkbox for "Block until the triggered projects finish their builds" is On.

If I start both of the wrapper projects ("Compile-64" and "Compile-32") they both kick off an instance of "Compile", as one would expect.

Unfortunately, those triggered instances of "Compile" never actually begin – they remain pending, because our only two Executors are occupied by the blocked wrappers.

A classic deadlock caused by the blocked builds still occupying an executor...

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Nov 5, 2019, 3:32:01 AM11/5/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages