On Mon, Oct 5, 2020 at 3:38 AM Oleg Nenashev <
o.v.ne...@gmail.com> wrote:
> jenkinsci/jnlp-agents […has] images for Maven, Ruby, .NET Core, Python. Node.js, etc.
I see. For example:
https://hub.docker.com/r/jenkins/jnlp-agent-ruby
https://github.com/jenkinsci/jnlp-agents/blob/34919e3fd9c28716ca49e1777eec6eb6eefa0635/ruby/Dockerfile#L3-L8
Useful for single-container agents. (For the `kubernetes` plugin we
typically encourage use of the `container` step so that the neutral
`jenkins/inbound-agent` is used with a third-party image in the pod.
Suffers from `ENTRYPOINT` and `USER` and `VOLUME` problems just like
the `withDockerContainer` step, as opposed to the style exemplified by
the `dockerNode` step; neither option is attractive but it is hard to
shoehorn Jenkins Remoting & workspaces into a container world.)
> These images will be hosted in the experimental DockerHub org (jenkins4eval)
Yes, makes sense.