> The docker plugin deals with images not containers - basically it does a
> docker run on the image, and then can, optionally, keep the container at
> the end of the run (but cannot be reused in a subsequent job I believe)
>
> It currently always tears down the container at the end of the Jenkins
run, as I suspect this is what most people want, as they're so cheap to
spin up.
The later versions allow you to also optionally tag and push to a
centralised repository at the end of the run. This could, in theory, allow
you to build a CI pipeline based on docker images.
I.E: (Job A)-+->(Job B)
|
--->(Job C)
Job A completes, pushes it's container back to a centralised repo and marks
the build with the ID of the container. Jobs B and C both pull that
container on start.
It's a bit nascent at the moment. The registry push is there but it's not
hugely tested (pesky time constraints).
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
