-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Windows 7 x64 master and slaves running Java7
我们使用此功能只允许使用 cuda 设备的有限数量的作业（请参阅配置截图）。从 1.536 版开始，这似乎不再起作用，因为在标签为“gpu”的节点上执行了多个具有“CUDA”类别的作业。
- duplicates
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
[JENKINS-20211] Pairs of throttled node labels no longer seem to work starting from version 1.536
| Description | Original: We use this feature to allow only a limited number of jobs which use a cuda device (see screenshots for configuration). Starting with version 1.536 this no longer seems to work because several jobs with the "CUDA" category are executed on a node with the label gpu. | New: We use this feature to allow only a limited number of jobs which use a cuda device (see screenshots for configuration). Starting with version 1.536 this no longer seems to work because several jobs with the "CUDA" category are executed on a node with the label "gpu". |
| Link |
New:
This issue is related to |
I can no longer reproduce the problem with Jenkins 1.544 and Plugin 1.8.1.
Anyone still able to reproduce this issue on recent Jenkins + Plugin versions?
Dwane Pottratz
added a comment - I am currently seeing this issue.
Jenkins 1.609 with Throttle 1.8.4
I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9.
I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work.
Dwane Pottratz
added a comment - I am currently seeing this issue.
Jenkins 1.609 with Throttle 1.8.4
I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9.
I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work. 
Peter Triesz
added a comment - We also experience this. We have several Multi-configuration projects and we use several Multi-Project Throttle Categories. Throttling config worked originally but lately executions stopped respecting these constraints.
We have upgraded to Jenkins 1.609 with Throttle 1.8.4 but the issue still persists.
We tried throttling on global level and leave 0 in the project configs, as well as setting 1 everywhere but none of the setting combinations worked.
We do not use the Priority Sort Plugin.
Peter Triesz
added a comment - We also experience this. We have several Multi-configuration projects and we use several Multi-Project Throttle Categories. Throttling config worked originally but lately executions stopped respecting these constraints.
We have upgraded to Jenkins 1.609 with Throttle 1.8.4 but the issue still persists.
We tried throttling on global level and leave 0 in the project configs, as well as setting 1 everywhere but none of the setting combinations worked.
We do not use the Priority Sort Plugin.
After downgrade to 1.535 throttling seems to work again.