-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.176.3
Hi Team,
I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected but when I trigger the throttle job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered if already 3 jobs were running. The return code using curl command is 302 and please find attachment for the same.
- is duplicated by
-
JENKINS-48591 Concurrent Builds Plugin Does not work properly
-
- Resolved
-
-
JENKINS-65884 Throttle concurrent builds plugin
-
- Resolved
-
[JENKINS-61485] Throttle Concurrent Builds not working when triggered from another job
Description |
Original:
Hi Team, I have instally throttle concurrent build recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected and when I trigger the job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered. Kindly fix this |
New:
Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected and when I trigger the job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered. Kindly fix this |
Summary | Original: Concurrent build not working when triggered from another job | New: throttel Concurrent build not working when triggered from another job |
Summary | Original: throttel Concurrent build not working when triggered from another job | New: throttle Concurrent build not working when triggered from another job |
Description |
Original:
Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected and when I trigger the job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered. Kindly fix this |
New:
Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected but when I trigger the throttle job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered if already 3 jobs were running. Kindly fix this |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] | |
Environment | New: Jenkins 2.176.3 |
Attachment | New: Capture.PNG [ 50687 ] |
Description |
Original:
Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected but when I trigger the throttle job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered if already 3 jobs were running. Kindly fix this |
New:
Hi Team, I have installed throttle concurrent build plugin recently to run only 3 jenkins pipeline job in parallel and the remaining should wait in queue. When i trigger the job manually it works as expected but when I trigger the throttle job from another jenkins job using curl command or jenkins trigger parameter the throttle build job doesn't wait in queue and job is not even getting triggered if already 3 jobs were running. The return code using curl command is 302 and please find attachment for the same. |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
coloradorob describes another reported instance of this issue in JENKINS-48591 (comment).