title: Can Jenkins nodes be given priority for build jobs
body: <p>I have a set of build jobs in jenkins that can run in any one of 3 build nodes.  They are all labeled with a common label of "ubuntu_build".  Each of the nodes has a number of executors thus allowing some of the builds to execute in parallel on a machine.  The setup is running fine and does what it is supposed to but I would like to improve it.</p>
  
  <p>The 3 build nodes have varying performance.  The first is twice as fast as the second which is twice as fast as the third. (call them fast_node, regular_node, slow_node)  </p>
  
  <p>As I understand the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Schedulingstrategy" rel="noreferrer">scheduling strategy</a>, the machine that was used last for a given build job will be preferred the next time around.  This can sometimes lead to issues when there are not many builds going through and the jobs were last built on slow_node and thus it keeps going there even though fast_node has some executors that could work.</p>
  
  <p>What I would like is a way to say that for any job coming through the queue I would like it to try to find room on fast_node, then regular_node, then finally slow_node.  (ie. try to keep using the fastest executor that is available)</p>
  
  <p>Is there anyway to set something like this up?</p>