It applies there in principle, but I do not see a major use case for "ssh-agent" tool being ran as a Docker container. OTOH I might be wrong: https://hub.docker.com/r/nuodb/ssh-agent
Personally I do not feel strongly about the name, and I am ready to follow the majority here. So far we are at 50/50 without clear majority. How could we get it? - Governance meeting voting? The majority of contributors do not show up there nowadays - This mailing list? - Twitter poll? Can do it right away, but it creates more visibility than educated feedback by voters Regarding the current status, we have already merged "jenkins/ssh-agent" and fixed the delivery Pipelines for it, for both Linux and Windows flows. Renaming is easy, because now we know all the pitfalls. Best regards, Oleg On Tuesday, April 14, 2020 at 12:26:49 PM UTC+2, Daniel Beck wrote: > > > > On Mon, Apr 13, 2020 at 10:52 PM Oleg Nenashev <[email protected] > <javascript:>> wrote: > >> My pull request is already built for "ssh-agent", so I will go ahead and >> setup DockerHub builds for this image. >> > If there are strong opinions, we have 1-2 extra days to revisit naming >> before the blogpost is shipped. >> > > AFAIUI, ssh-slaves wasn't called "SSH Agents" plugin less because of "SSH > Agent" plugin, but more because of the confusion around "ssh-agent" the > program. > > Why does this not apply here? > -- 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/ec044ca0-ac12-4c18-be8b-57cc6f3990d9%40googlegroups.com.
