I have several cloud templates defined, each pointing to a different physical node that can run our build containers.  I have several templates defined under each cloud.  I have a common label defined on each template across the clouds.  I have defined a node preference score on each template.  However, now matter what I set the preference score to, Jenkins always uses the first cloud and template defined.  it will use that template until it reaches the instance cap. then moves to the next one.  This is not good utilization of the resources.  

  Should the node preference score be working?  is there any other way to control how Jenkins utilizes the container templates?