" I do agree that certain issues should fail immediately (image not found). Certain other issues should perform exponential backoff (Cloud infrastructure down). Provisioning limits could be annoying though, would be interesting if they could be left in the queue until Jenkins side provisioning limits are not violated. I am not sure how to handle an environment like Kubernetes though where other entities may be utilizing resources and you have to "share". "
This is something we have in mind. Provisioner could wait for available resources before it creates a Slave, leaving the task in the queue with a LabelAssignment waiting for matching executor. Would anyway need to let the Run start *then* create the slave, which means some race condition could appear and the required resources aren't available for this Slave to start even they were, few ms before - or we need some way to reserve resources on the infra, which then would significantly limit the available implementations. Maybe then we could cancel the Run, as we run early in it's lifecycle, and re-schedule it as a task in the Queue, claiming the Run never existed ? 2016-03-09 21:40 GMT+01:00 Jesse Glick <[email protected]>: > On Wed, Mar 9, 2016 at 11:52 AM, Suckow, Thomas J > <[email protected]> wrote: > > Certain other issues should perform exponential backoff (Cloud > > infrastructure down). > > Or just fail the build and the next one should work. > > > It could also handle the logic of some users wanting to configure slaves > on > > a per job basis. > > If you mean “configure Docker images on a per-job basis”, this is > addressed by both the Docker Custom Build Environment and Docker > Pipeline plugins, both of which ought to move toward using this new > infrastructure. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3ycEVavhfm2Kuj5pOB5fkPF6vaOJfb6Zu-89y%2BQRm95g%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzke%3D_zx5%2BupiXp7ZBwnzwCLmvcnnUr-Hms%2BvGJ9ii13tg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
