[JIRA] (JENKINS-61779) Regression: Job stock in queue waiting forever after upgrade

2 views
Skip to first unread message

peter@softwolves.pp.se (JIRA)

unread,
Apr 2, 2020, 7:14:02 AM4/2/20
to jenkinsc...@googlegroups.com
Peter Krefting created an issue
 
Jenkins / Bug JENKINS-61779
Regression: Job stock in queue waiting forever after upgrade
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: waiting.png
Components: core, throttle-concurrent-builds-plugin
Created: 2020-04-02 11:13
Environment: Jenkins 2.222.1
throttle-concurrents 2.0.2
Debian GNU/Linux 10.3 amd64
Java 11.0.6+10-post-Debian-1deb10u1
Labels: regression throttle
Priority: Minor Minor
Reporter: Peter Krefting

I "apt dist-upgrade"-d my build Jenkins server, and was updated from 2.204.4 to 2.222.1, and now I am running into issues.

The major issue is that my throttled builds do not work. I have a build (see attached creenshot)
that is configured with throttling:

<hudson.plugins.throttleconcurrents.ThrottleJobProperty plugin="throttle-c...@2.0.2">
<maxConcurrentPerNode>1</maxConcurrentPerNode>
<maxConcurrentTotal>1</maxConcurrentTotal>
<categories class="java.util.concurrent.CopyOnWriteArrayList">
<string>vm-installer</string>
<string>kickstart-repo</string>
</categories>
<throttleEnabled>true</throttleEnabled>
<throttleOption>category</throttleOption>
<limitOneJobWithMatchingParams>true</limitOneJobWithMatchingParams>
<matrixOptions>
<throttleMatrixBuilds>false</throttleMatrixBuilds>
<throttleMatrixConfigurations>true</throttleMatrixConfigurations>
</matrixOptions>
<paramsToUseForLimit></paramsToUseForLimit>
<configVersion>1</configVersion>
</hudson.plugins.throttleconcurrents.ThrottleJobProperty>

It is set up to build on a single node:

<hudson.matrix.LabelAxis>
<name>label</name>
<values>
<string>kickstartbuild</string>
</values>
</hudson.matrix.LabelAxis>

The pop-up says that is waiting for the next available executor, which is "master", which is the only one satisfying this label. It is idle, but Jenkins is still waiting.

The configuration worked fine before upgrading. Restarting Jenkins does not help.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages