I have no religious conviction to the java library used, nor the plugin. So, I'm going to take a two prong approach from here:
1. Test the master docker-plugin to see how the JNLP and latest docker-java PRs address my use cases. Once I have a bearing on things, I'll work to submit any PRs I can to help. 2. I'm going to maintain the docker-ephemeral-cloud-plugin and get it to a 'production ready' state. I'm using it for enough workloads that I feel it's worth finishing out. I strongly feel that this plugin should not do anything more than act as a highly opinionated slave provisioner. Therefore, I won't be adding features like build steps, additional launchers, etc. PPS From tech viewpoint i see that "ephemeral cloud" has queue lock issues > and shading. But if this plugin solves user issue, then it should be hosted > and allow people experiment on it. > > Thanks for looking and finding these! I noticed the queue lock issues, but I haven't jumped into debugging it yet. Any hints or tips on where to chase that? Thanks, Kevin -- 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/8ddca205-ee0f-4e3b-be70-daffca4c9fba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
