Beam was just discussing this. Was there any conclusion? Is there an ASF Infra
build cache? Or is there now a project that did it themselves we can learn from?
On 2019/12/29 12:15:59, Vladimir Sitnikov wrote:
> >Trying to get the use case
>
> Please check the first mail. It is there.
>
> For
>Trying to get the use case
Please check the first mail. It is there.
For instance:
A) checkout master branch. Run the build.
It would be much faster as it won't have to rebuild and retest all the
things.
B) Pull request testing. It would save time on skipping the bits, thus it
would produce fe
Trying to get the use case
Le dim. 29 déc. 2019 à 07:52, Vladimir Sitnikov
a écrit :
> >You should use Jenkins to cache between builds
>
> I want to reuse the same cache at developers' machines and at Travis /
> GitHub Actions.
>
> Caching between Jenkins runs is not enough.
>
> Vladimir
>
>You should use Jenkins to cache between builds
I want to reuse the same cache at developers' machines and at Travis /
GitHub Actions.
Caching between Jenkins runs is not enough.
Vladimir
You should use Jenkins to cache between builds
Jeff
Le sam. 28 déc. 2019 à 21:19, Vladimir Sitnikov
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.
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 cou