|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Magnus,
thank you very much for investigating this issue. As I will keep working with your plugin the next weeks and months I will definitivily try out your latest version and post the results of what exteded logging tells me.
Workaround:
With your help I was able to find two simple workarounds. You told me to activate parallel builds in the job settings. This results in the job being build, guess?,...in parallel. Thus, no queue was created for me anymore, as all jobs were build at the same time. The first solution, which is obviously not the best, was to reduce the number of processors in the Jenkins settings. As this number represents the number of Jobs being build in parallel, as every core usually is capable to compute one of them.
The more advanced solution is to install the Throttle Concurrent Builds Plug-in which allows you to set this limitation PER JOB. Reducing this throttle setting to 1 and allowing parallel builds got me the behaviour I expected. Now I can trigger Jobs (especially the same job multiple times) with a priority parameter and they are getting queued as expected with only one job build at a time.
With best regards,
Marcus