I'm not sure if it's helpful, but I believe Travis CI runs the following command during the install phase to download dependencies: mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V
For more info: https://docs.travis-ci.com/user/languages/java/#Maven-Dependency-Management On Mon, Oct 2, 2017 at 12:52 PM Benedikt Ritter <brit...@apache.org> wrote: > Hello Laird > > > Am 02.10.2017 um 18:42 schrieb Laird Nelson <ljnel...@gmail.com>: > > > > On Wed, Sep 27, 2017 at 4:53 AM Benedikt Ritter <brit...@apache.org> > wrote: > > > >> I have a CI Build in GitLab, where I want to define a job that downloads > >> all the artifacts which are needed for the different lifecycle phases > and > >> plugin executions as well as all project dependencies. I only want to > >> download all the stuff once and then copy the artifacts between the > build > >> stages. > > > > > > Have you looked at the cache directive ( > > https://docs.gitlab.com/ee/ci/yaml/#cache) and a custom settings.xml > with a > > <localRepository> element instead of using artifacts? > > There is no need for a custom settings.xml, since you can set the local > repository using MAVEN_OPTS. This can be done with a top level variables > declaration in .gitlab-ci.yaml. > > The cache directive won’t help you here, since it will cache dependencies > between pipeline runs. I don’t think this is a good idea. I like my CI > builds to run from a clean environment. However for one pipeline run, I > want to download all dependencies upfront. But this does not seem to be > possible. > > Cheers, > Benedikt > > > > > Best, > > Laird > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
