-
Improvement
-
Resolution: Unresolved
-
Major
-
None
Provide a job option that allows jobs found from polling to be added to the queue even when there is another job running.
Current Behavior:
Poll finds job and starts it.
If job is still running the next time a poll occurs no jobs are added to the queue and the following message is reported: _ "Build in progress, polling delayed."_
Desired Behavior:
Poll finds job and starts it.
If job is still running the next time a poll occurs a job is queued.
Current Workaround:
- Shorter polling periods so there is less delay after the previous job completes.
- Set 'Execute concurrent builds if necessary' and use Perforce change-submit triggers to trigger Perforce job.
- is related to
-
-
- Closed
-
[JENKINS-41849] Optionally queue polled jobs
Karl Wirth
created issue -
Karl Wirth
made changes -
| Description |
Original:
Provide a job option that allows jobs found from polling to be added to the queue even when there is another job running. Current Behavior: Poll finds job and starts it. If job is still running the next time a poll occurs no jobs are added to the queue and the following message is reported: _ "Build in progress, polling delayed."_ Desired Behavior: Poll finds job and starts it. If job is still running the next time a poll occurs a job is queued. Current Workaround: Shorter polling periods so there is less delay after the previous job completes. |
New:
Provide a job option that allows jobs found from polling to be added to the queue even when there is another job running. Current Behavior: Poll finds job and starts it. If job is still running the next time a poll occurs no jobs are added to the queue and the following message is reported: _ "Build in progress, polling delayed."_ Desired Behavior: Poll finds job and starts it. If job is still running the next time a poll occurs a job is queued. Current Workaround: * Shorter polling periods so there is less delay after the previous job completes. * Set '_Execute concurrent builds if necessary_' and use Perforce change-submit triggers to trigger Perforce job. |
Karl Wirth
added a comment - Hi fkykko I've increased the priority on this. We are in the middle of implementing a couple of large features but will add this to the backlog of things to be looked into.
Karl Wirth
added a comment - Hi fkykko I've increased the priority on this. We are in the middle of implementing a couple of large features but will add this to the backlog of things to be looked into. Karl Wirth
made changes -
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Karl Wirth
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
p4karl Ok, thanks. Also note that the "Workaround" does not work for pipeline jobs since it does not have the checkbox "Execute concurrent builds if necessary"
Staffan Forsell
added a comment - - edited p4karl Ok, thanks. Also note that the "Workaround" does not work for pipeline jobs since it does not have the checkbox "Execute concurrent builds if necessary" Staffan Forsell
made changes -
| Link |
New:
This issue is related to |
Staffan Forsell
added a comment - p4karl or p4paul: Any news on this? This is blocking having our long running pipelines execute for each submitted changelist. This could simplify finding the exact changelist that broke the build.
Staffan Forsell
added a comment - p4karl or p4paul : Any news on this? This is blocking having our long running pipelines execute for each submitted changelist. This could simplify finding the exact changelist that broke the build. Karl Wirth
added a comment - Have discussed with Paul and in the current Jenkins framework we have some ideas of how this can be implemented. We'll take a look.
Karl Wirth
added a comment - Have discussed with Paul and in the current Jenkins framework we have some ideas of how this can be implemented. We'll take a look.
p4karl With long running pipelines in docker containers, for us this is actually more than a "minor" issue. I would really like to get this done I order to get triggered builds per change.