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/CANMVJznmnydODNX%2BYXmh0ujnJXsoZWcPT%2BpJCWwdR0_wUpfDTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
