We use freestyle jobs which allow concurrent builds. Sometime we have 10+ builds running at the same time, distributed across a number of agents. We use the https://wiki.jenkins.io/display/JENKINS/Throttle+Concurrent+Builds+Plugin as well.
Some of our agents are slower than others. Unfortunately, when Jenkins starts a new build, by default the agent selected is the last one used (provided it has a free executor). That means that once we use a slow agent, we tend to stay on it. Is there any way to better control the selection of which agent to run on? Do pipelines offer anything extra in this area? Thanks Matthew -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eb994b4616a0453aa794f5bb3b9f8619%40Diamond.ac.uk. For more options, visit https://groups.google.com/d/optout.