You should use Jenkins to cache between builds Jeff
Le sam. 28 déc. 2019 à 21:19, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> a écrit : > Hi, > > Does anybody know if there's a Build Cache server for Gradle available in > ASF infrastructure? > > --- > > The use case is as follows: the server saves build artifacts (e.g. jars, > javadocs, etc), and > it helps to save build times on the repeated inputs. > > For instance, in a multi-module project, we could save time on rebuilding > non-modified modules. > In the same way, we don't need to verify code style if we have already > verified it for the same set of input files. > In the same way, we don't need to execute unit tests if we have already > executed tests for the same source base. > > The build cache would speedup build after a clean checkout, and it could > save developer's time (and PR testing time). > > --- > > There's a free implementation available > https://docs.gradle.com/build-cache-node/ (it is a Docker image) > > The suggested workflow is: > 1) Build cache is writable only from ASF infrastructure (e.g. from ASF > Jenkins job). > In other words, ASF Jenkins builds the project and updates the cache > 2) Everybody uses the cache in read-only mode, so they don't spend time on > what was already built by CI server. > > Vladimir >
