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/4c40a319-5da2-455d-a364-a1b70aae810a%40googlegroups.com.

Reply via email to