>
>
> We also considered to offer an option to cache some path, comparable to
> travis-ci approach (based on tar.gz), so typically let end-user configure
> maven local repository as "cached". Backed could rely on additional volumes
> for this purpose, but definitively not on bind-mounts :P.
The whole build agent root directory is managed as a docker volume, and
retrieved from previous build, so you can easily benefit such caching if
you configure maven to use adequate path for local repository (which should
be the case by default, as /home/jenkins is slave root).
We also
Hi, Nicolas,
One example I can think of: for maven build, we want to cache the
downloaded dependencies so we don't have to download them every time.
So in that case, I was thinking to cache on the host, or a data volume. Any
suggestions?
Thanks,
Qiang
On Saturday, October 15, 2016 at
Thank you for posting the response ! I do need to rethink my strategy now. Even
though I need to solve legacy problems in a short term , I agree that it does
not become a requirement :)
So for moving data between containers , what options can I explore ? And is
there instruction to use side
Hi,
There's no technical limitation to use this option (we actually already
support it to allow docker.sock bind mount on a dedicated side container),
but our experience is most user use this for bind-mount, which result in
permission issues and in most case are just short terms workarounds to
