I resolved a similar situation (both Light and Heavy jobs) by creating two slaves for the 'strong' machines.
Each weak machine has one slave, with a 'weak' label and several executors. Each strong machine has two slaves: Strong_machine1, labeled 'strong', with 1 executor Weak_machine1, labeled 'weak'. with several executors. Heavy jobs are configured to only run on 'strong' label. Light jobs are configured to only run on 'weak' label. We have not yet had problems because of light jobs running on the same machine as a heavy one. vineri, 18 martie 2011, 14:53:21 UTC+2, pgweiss a scris: > > I just had a look at the source and I don't think so. I would only want > one or maybe two jobs with assigned priorities. The remainder I would > want FIFO. I guess a combination would work. That is, assign each job a > priority, with a default. Within each priority class sort by FIFO. > > What would really make this scheme useful is some UI support so that > priorities of jobs in the queue can be raised or lowered dynamically. > > -P > > > On Thu, 17 Mar 2011 17:43:06 -0400, Sami Tikka <[email protected]> wrote: > > > Would http://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin > > meet your needs? > > > > -- Sami > > > > 2011/3/17 Paul G. Weiss <[email protected]>: > >> As I wait for my Jenkins jobs to run, a feature suggests itself. > >> > >> I have many different kinds of jobs and many different slaves. One > >> slave is > >> a lot "beefier" than the others, and there is a particular job, call it > >> "Heavy", that just runs a lot faster on that slave than others. So I > >> always > >> want to run that job on this slave. > >> > >> So right now, I tie that job to the slave, and I reserve the slave for > >> tied > >> jobs only, because I want it to be available in case "Heavy" needs to > >> run. > >> This means that the slave is often idle. > >> > >> What I'd like to do is configure the slave to give priority to "Heavy". > >> That way, I don't have to reserve it for tied jobs only, but if there > >> is an > >> instance of Heavy in the queue, then my slave will finish whatever job > >> it is > >> currently running and process Heavy next. It gets to cut the line. > >> > >> Is this useful? Is this better than assigning jobs priority in general? > >> > >> -P >
