*you* just said you aren't working anymore on this plugin. So why complain ?
2016-03-05 16:31 GMT+01:00 Kanstantsin Shautsou <[email protected]>: > `You've been removed from the Jenkins team docker-plugin Developers` > Thanks to anonymous person, removing person from team would be a great > benefit to this plugin! ;) > That a bit offtop, please continue with the initial topic. > > > On Saturday, March 5, 2016 at 11:47:09 AM UTC+3, Kanstantsin Shautsou > wrote: >> >> >> On Mar 5, 2016, at 11:15, nicolas de loof <[email protected]> >> wrote: >> >> >> >> 2016-03-05 7:36 GMT+01:00 Kanstantsin Shautsou <[email protected] >> >: >> >>> I made my plugin after @stephenc comments and seems that his work >>> somebody finally tried to expose >>> https://github.com/jenkinsci/mansion-cloud-plugin/pull/9 According to >>> stephenc comments such logic should be generic and would make sense for all >>> cloud plugins, that’s why i made separate plugin. >>> >>> @batmat if you are using docker-plugin then it may have synchronisation >>> or logic issues. >>> >> >> @KostyaSha is this something you're trying to address with you >> "yet-another-docker-plugin" ? Are you working on both plugins ? >> >> I’m not maintaining docker-plugin anymore (reasons described in >> readme). I had good experience with migrating static ssh slaves to >> docker-plugin, but it had not enough stability. In yad-plugin i just >> continue the work and want get stable and faster provisioning for standard >> Cloud slaves (for integration tests invented remote run and configuration >> of master instance and started working on jmeter plugin for doing >> performance tests). Delays mostly not a cloud plugin issue, so experimental >> “faster” i placed in separate plugin. In yad-plugin and docker-java library >> i almost resolved all related issues and hope it will work good, stable and >> covered with ITs. >> For future I have some experimental ideas for DSLs, but they may >> duplicate existing features with the difference that i will use >> docker-java. Even if nobody will use it, i would have reference >> implementation for docker-java where i’m co-maintainer. For example it >> should be possible to expose globally configured docker connection into >> JobProperty configuration (that of course will use QTD for hacks), but that >> would raise questions about limits and security. Everything depends on free >> time and mood :) >> >> yad-plugin - is released into UC (it my experiment to host it under >> personal account). >> faster-node-provision-plugin >> <https://github.com/KostyaSha/faster-node-provision-plugin> - isn’t >> released as i had no final conclusion on it’s stability (maybe it would >> require to substitute the whole provisioning strategy). If stephenc will >> finally review and bless then it would make sense to fork and release it. >> >> >> >>> On Mar 5, 2016, at 01:50, Baptiste Mathus <[email protected]> wrote: >>> >>> >>> 2016-03-04 21:14 GMT+01:00 Kanstantsin Shautsou < >>> [email protected]>: >>> >>>> 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 <[email protected]>: >>>>>>> >>>>>>>> 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 [email protected]. >>>>>> 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 [email protected]. >>>> 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 a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/WV6sPmIh-tk/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7kb2RkXzgQPrv7SS%2BCJVsV79q17sHsVE6pzYXrCh3QHw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7kb2RkXzgQPrv7SS%2BCJVsV79q17sHsVE6pzYXrCh3QHw%40mail.gmail.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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/F0D26341-CD48-4C8C-BBF2-8F69CF060B12%40gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/F0D26341-CD48-4C8C-BBF2-8F69CF060B12%40gmail.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 a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/WV6sPmIh-tk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznxr4jD_hu8JYTS%3DEa%2B84Y6uVA0mr10XSTe76%2BHxcmDmA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznxr4jD_hu8JYTS%3DEa%2B84Y6uVA0mr10XSTe76%2BHxcmDmA%40mail.gmail.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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/c027feb0-3b86-4dfd-bd83-7dafc8c7d743%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/c027feb0-3b86-4dfd-bd83-7dafc8c7d743%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznqSHnpf0H-hZA2fiqJ_mPNbR0d4b2nW5uGUefvH%2B9bew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
