I was hoping that these dependencies could be cached somewhere in the workspace instead or relying on Gradle specific things. We have the same thing for NPM related dependencies. Continuous downloading of the related dependencies is just to slow.
On Thursday, June 23, 2016 at 8:48:32 AM UTC+2, Craig Rodrigues wrote: > > In 2011, this discussion thread talked about this topic: > https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525 > > and it didn't seem possible. > > However, I advise you to post your question to https://discuss.gradle.org/ > , because there may be new information that can make this possible. > > -- > Craig > > > On Wed, Jun 22, 2016 at 4:48 AM, Marco Pas <marco....@gmail.com > <javascript:>> wrote: > >> Now that we have a first successful build using a Jenkinsfile Pipeline we >> are looking on how to cache downloaded dependencies. >> Currently when we build our Gradle applications the dependencies are >> downloaded each time the Docker Slave is executed on a remote host. Is >> there a way to cache the downloaded dependencies for later reuse so we can >> speedup the build process? >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a5effc39-cfeb-4f11-a639-7cfa61a4a044%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
