Docker client in jnlp slave about docker-agent HOT 5 CLOSED

Based on this approach I wrote this article that tries to better explain how to achieve what I was trying to say - article here.

from docker-agent.

Assuming I use this exact image I only get an environment with JDK, right? What if I want to build other types of projects?

You can create your own image on the top of this image.

So what is the accepted way of building multiple types of projects...

If you have images for other tools including the tool you need and JDK, you can use multiple images within your build flow by using Jenkins Pipeline and shared workspaces. Useful plugins: Docker Pipleline Plugin, External Workspace Manager Plugin

from docker-agent.

You can create your own image on the top of this image.

Yes, I know I can build images on top of this base image, but the idea is that for every project I want to build I have to create a new image, then configure a separate pipeline (with a new Docker image I have to manage) - which I don't really want to do and seems a bit overkill.

I understand this is the way of doing right now, but how about the approach I suggested above? Is this something we might want to use? (at least from the simplicity point of view?)

Thanks!

from docker-agent.

the kubernetes plugin allows now multi-container agents, so you can reuse the images from the hub without needing to extend this one. I think that covers the use case you are mentioning

from docker-agent.

Yes, the example you provided covers the use case I exemplified.
Closing this. Thanks!

from docker-agent.