Hi Jesse, There are official images like jenkinsci/docker-ssh-agent <https://github.com/jenkinsci/docker-ssh-agent> or jenkinsci/docker-inbound-agent <https://github.com/jenkinsci/docker-inbound-agent>. They are technology-neutral. jenkinsci/jnlp-agents <https://github.com/jenkinsci/jnlp-agents> is a separate story, because it actually provides technology-specific images hosted within the official Jenkins DockerHub account. There are images for Maven, Ruby, .NET Core, Python. Node.js, etc. there. So these images are well aligned with what U suggest for Jenkinsfile Runner.
To address concerns about supportability, I have no intent to publish the provided images as "official" ones in foreseeable future. Jenkinsfile Runner 1.0 and new packaging flows need to be released first. These images will be hosted in the experimental DockerHub org (jenkins4eval), and the documentation will include proper disclaimers. I hope it addresses your concern. Best regards, Oleg On Friday, October 2, 2020 at 4:22:16 PM UTC+2 Jesse Glick wrote: > On Fri, Oct 2, 2020 at 8:50 AM Oleg Nenashev <o.v.ne...@gmail.com> wrote: > > We already have similar images for inbound agents > (jenkinsci/jnlp-agents). > > Well, not sure how similar—the official agent images are > technology-neutral, so have an entirely different scale of maintenance > effort involved. I think what you are proposing is more akin to > hosting and maintaining official Docker images such as `maven`. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8771d6b3-1a86-435e-923d-2b0e1e985b1dn%40googlegroups.com.
