On Tue, Sep 5, 2017 at 8:28 PM, Oleg Nenashev <[email protected]> wrote: > […] while it's still compatible with Docker Plugin use-cases
One of my reservations about both the `docker-plugin` and the `yet-another-docker-plugin` (BTW both incorrectly include `-plugin` in the `artifactId`) is that they try to solve too many things, and are cluttered with various builders you do not really need. A plugin should either focus on letting a job request an image for specific build steps, as `docker-workflow` and `docker-custom-build-environment` do; or provide a solid `Cloud` implementation for the case that the whole agent JVM runs inside a globally configured container (IMO the main reason to use `docker-plugin`); or something in between, as `docker-slaves` creatively attempts. -- 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/CANfRfr04rUG_93UkFQv3vwqMVxvnWfE8RFUaQ-C%2B3jRy%2BvAWKw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
