Thanks for your kind words :). I understand. At a high level, they both aim to deliver slaves using Docker. This is an old problem; do you break away and create new, or revise in place? I think we should move forward with the new one, and let it work itself out. I'm not opposed to merging, but I don't want to delay delivering immediate value to users. I created the plugin out of urgency (I couldn't get the firewall rules for 100+ SSH ports approved in my organization) and I feel others have similar needs. Before looking at merging the two, I would like to gain some more learning through user experience.
I recall we once had two Gerrit plugins, but have since seen the two combine into one excellent plugin. I believe the real horse race is between the underlying docker libraries. In the end, we'll likely have a clear winner, and can standardize a group of plugins around that. Perhaps docker-commons becomes that focal point, and we have smaller plugins that deliver slaves, build steps, workflow DSL, etc. For now, I think it's too early to settle. I don't want you to frown, but can we go ahead and move forward with this as-is? Thanks, Kevin On Monday, November 16, 2015 at 10:34:07 AM UTC-5, R Tyler Croy wrote: > > (replies inline) > > On Fri, 13 Nov 2015, kmbulebu wrote: > > > I'd like to introduce a new plugin for hosting on jenkins-ci.org, the > > docker ephemeral cloud plugin. > > > > Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud > > Github and Jenkins username: kmbulebu > > Name: docker-ephemeral-cloud-plugin > > > > Description: > > > > The Docker Ephemeral Cloud plugin provides an elastic pool of slaves, > using > > Docker containers, that live only as long as the job. When a job is > > scheduled, Jenkins checks for Docker image configurations that match the > > labels of the job. When one is found, Docker is invoked via REST APIs to > > pull the image and run the container. Within the container, the Jenkins > > JNLP slave jar is downloaded and run. Communication is established to > the > > Jenkins master and the new slave node performs the requested job. When > > complete, the container is stopped and removed. > > > > The key differentiators here are that this plugin enables stateless > slaves > > on containers, without the need for any port mappings, SSH servers, > docker > > clients, or existing slaves. The focus is on stateless jobs and builds > and > > not continuous deployment via containers. > > > > More on how this plugin differs from similar Docker > > plugins: > https://github.com/kmbulebu/docker-ephemeral-cloud#comparative-to-other-docker-plugins > > > > > The differences between this plugin and the Docker plugin don't seem very > major to me, is there an objection you would have to merging this with the > Docker plugin? That plugin already has many thousands of installations and > the > TLS support in particular I think would be useful as well. > > Have you also seen the Docker build step plugin, I believe that might > overlap > with your work as well, and already has a few thousand installations. > > > There's some really good work here and by merging efforts with the > existing > Jenkins/Docker plugins I think we can improve the usage for many existing > users > and help attract new ones. > > > > Let me know what you think, if you're open to it I'm happy to help where I > can. > > > If you're not keen on merging, then I suppose I'll make a frowney face and > setup the hosting, etc. > > > > Cheers > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > ------------------------------------------------------ > -- 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/c9ba5f44-73db-41ed-b6de-1f7719d01ab6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
