+1 to inbound agent rename What about just ssh-agent for the ssh one? We don’t need to worry about the plugin name clash here I think
Thanks Tim On Sun, 12 Apr 2020 at 09:36, 'Gavin Mogan' via Jenkins Developers < [email protected]> wrote: > sshd-agent? > > On Sun, Apr 12, 2020 at 1:12 AM Oleg Nenashev <[email protected]> > wrote: > >> Also, I am not sure about using "jenkins/ssh-build-agent" as an image >> name for SSH agents. Would appreciate opinions/suggestions. Maybe >> "ssh-outbound-agent" though it may sound greek to users? >> >> On Sunday, April 12, 2020 at 9:13:48 AM UTC+2, Oleg Nenashev wrote: >>> >>> While we are here, I suggest to rename "jenkins/jnlp-slave" to >>> "jenkins/inbound-agent" instead of merely replacing a single term. >>> "JNLP" terminology is also deprecated, and with WebSockets support it >>> creates even more confusion. >>> >>> BR, Oleg >>> >>> On Friday, April 10, 2020 at 11:06:38 PM UTC+2, Oleg Nenashev wrote: >>>> >>>> Dear all, >>>> >>>> We will be renaming Jenkins agent Docker images on Sunday/Monday in >>>> order to get rid of the "slave" terminology in image names. Scope: current >>>> "jenkins/slave", "jenkins/jnlp-slave" and "jenkins/ssh-slave" images. The >>>> renaming will involve renaming repositories on GitHub and re-configuring >>>> repositories on DockerHub. See INFRA-1105 >>>> <https://issues.jenkins-ci.org/browse/INFRA-1105> for more info. >>>> >>>> Potential impact: >>>> >>>> - There might be some disruptions for developers who rely on the >>>> images or use GitHub APIs to fetch repositories (no all APIs and GtHub >>>> Apps >>>> handle renaming correctly). >>>> - There should be no issues for Jenkins users, we will keep >>>> delivery flows for old naming so they will have time to migrate. >>>> - Migration period is TBD, because many components will need >>>> follow-up updates (e.g. some Docker and Kubernetes plugins), not to >>>> speak >>>> about user. I would suggest to target 1 year of support >>>> >>>> I will submit a blogpost with the migration summary once it is >>>> completed. >>>> >>>> Best regards, >>>> Oleg Nenashev >>>> >>>> >>>> >>>> >>>> >>>> -- >> 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/028ee530-2f2e-4131-ac99-2b499a7bbc1e%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/028ee530-2f2e-4131-ac99-2b499a7bbc1e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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/CAG%3D_Duu_%3DyiYCe6m_xKt7%3DmDbGO3%3DOMHXVfQyvP%3DQs7yMm9KfA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duu_%3DyiYCe6m_xKt7%3DmDbGO3%3DOMHXVfQyvP%3DQs7yMm9KfA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAH-3BifCPX0MUzEsMv6q09hQ39vmjJk8Ho2Wnh1F-wKk4LJmZQ%40mail.gmail.com.
