![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
03/Dec/12 1:35 PM
|
|
Description:
|
Consider the following scenario: There's a large number of different jobs configured that get triggered a lot all the time. Each of the jobs takes a considerable amount of time to run. On the other there's have a small number of jobs that run not that often and when they run they don't take very long.
The latter kind of jobs will suffer starvation by the other kind. If the small jobs are of higher importance for some reason then there's no easy way to priotize them. Even the "Priority Sorter Plugin" doesn't really help, because before the job at the top of the queue is scheduled a slot needs to become available which can take maybe an hour or two before one of the long running jobs completes.
What would be really great is to have the ability to configure slots at a similar level as nodes can be configured in respect to labels. I'd like to be able to reserve some slots for the one kind of jobs and some other slots for the other kind of jobs.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Matthias Gerstner
|
|
|
|
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
|
