![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
heavy-job |
|
Created:
|
26/Mar/14 10:52 AM
|
|
Description:
|
I have some jobs that can't/shouldn't be run concurrently with any other, e.g. a test where we want to measure the runtime with a large input; or a job that housekeeps all the sandboxes which can cause file locking issues. Heavy job plugin with weight set equal to the number of executors fixed my problem but if the number of executors would go up then other jobs would get in in parallel.
I propose that a special value, like 0 or "max" or "all" can be put in job weight and the heavy job plugin will occupy all executors.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Steve Carter
|
|
|
|
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.
