2016-03-04 21:14 GMT+01:00 Kanstantsin Shautsou <kanstantsin....@gmail.com>:
> Cloud delays in theory should be possible to avoid by: > 1) kicking suggestReview. I wrote plugin but had no ability to test on > huge installations > https://github.com/KostyaSha/faster-node-provision-plugin > 2) increasing one of coefficients for provisioner(or statistics collector, > forgot classname) (jglick is using it in demo's and i'm using in my > installations). > NodeProvisionner? Btw, that page might be related IIUC what you talk about. There're many seemingly (didn't test yet) useful infos about those coeffs and what they do: https://cloudbees.zendesk.com/hc/en-us/articles/204690520-Why-do-slaves-show-as-suspended-while-jobs-wait-in-the-queue- Btw, IIUC, this page might explain why I'm seeing my slave/agent docker containers being provisionned in between 5 seconds and roughly 6 minutes... > AFAIK the main jenkins pain is the Queue locks. How this plugin will deal > with locks? > > >>>> 2016-03-04 12:08 GMT+01:00 nicolas de loof <nicolas...@gmail.com>: >>>> >>>>> Hi folks, >>>>> >>>>> Yoann and I have extracted from our docker-slaves hack-ish pet project >>>>> a stable sub-component so a plugin can manage slaves that are dedicated to >>>>> a Build, not relying on Cloud API, and get them tied to a Build. i.e Slave >>>>> and Build share a common lifecycle. If Slave fails to start, Build will >>>>> fail as well. If slave is slow to start (maybe pulling a huge docker >>>>> image), build log will report the progress. >>>>> etc. >>>>> >>>>> design and use-case : >>>>> https://wiki.jenkins-ci.org/display/JENKINS/One-Shot+Executor >>>>> code : https://github.com/jenkinsci/one-shot-executor-plugin >>>>> >>>>> the current code base do rely on hacks, our goal is to demonstrate >>>>> this use case (can be tested reusing sample >>>>> <https://github.com/jenkinsci/one-shot-executor-plugin/blob/master/src/sample/java/org/jenkinsci/plugins/dockerprovisioner/DemoOneShotProvisioner.java>) >>>>> so we can get the adequate hooks introduced in jenkins-core and later >>>>> re-implement same API on a cleaner basis. >>>>> >>>>> >>>>> >>>>> >>>> -- >>> 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 jenkinsci-de...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/f5935828-61d5-4afa-afab-9090deacb19e%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/f5935828-61d5-4afa-afab-9090deacb19e%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/d65c0d1f-e298-4e08-b5f9-15f883b55f12%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/d65c0d1f-e298-4e08-b5f9-15f883b55f12%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7kb2RkXzgQPrv7SS%2BCJVsV79q17sHsVE6pzYXrCh3QHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
