You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Vladimir Sitnikov (Jira)" <ji...@apache.org> on 2021/02/04 14:29:00 UTC
[jira] [Updated] (CALCITE-4140) Configure Gradle Remote Build Cache
to speedup builds
[ https://issues.apache.org/jira/browse/CALCITE-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Sitnikov updated CALCITE-4140:
---------------------------------------
Description:
Gradle build cache enables to reuse build artifacts across different build executions: https://docs.gradle.org/current/userguide/build_cache.html
For instance, if linq4j code is not modified, its `compileJava` and `javadoc` results can be reused in the other builds (e.g. PR builds).
{{test}} tasks should probably not be cached as the tests often include integrations with databases, so we should execute them from scratch.
Note: the cache is sensitive to Gradle version, Java version, and extra files in the workspace, so the common practice is to seed the cache only from CI jobs.
There's ticket for ASF build cache: https://issues.apache.org/jira/browse/INFRA-20516, however, it is likely we won't be able to use it in GitHub Actions :-/
An alternative option is to setup AWS S3-backed cache via https://github.com/burrunan/gradle-s3-build-cache
---
Note: the remote build cache can be disabled with {{-Ps3.build.cache=false}}
was:
Gradle build cache enables to reuse build artifacts across different build executions: https://docs.gradle.org/current/userguide/build_cache.html
For instance, if linq4j code is not modified, its `compileJava` and `javadoc` results can be reused in the other builds (e.g. PR builds).
{{test}} tasks should probably not be cached as the tests often include integrations with databases, so we should execute them from scratch.
Note: the cache is sensitive to Gradle version, Java version, and extra files in the workspace, so the common practice is to seed the cache only from CI jobs.
There's ticket for ASF build cache: https://issues.apache.org/jira/browse/INFRA-20516, however, it is likely we won't be able to use it in GitHub Actions :-/
An alternative option is to setup AWS S3-backed cache via https://github.com/burrunan/gradle-s3-build-cache
> Configure Gradle Remote Build Cache to speedup builds
> -----------------------------------------------------
>
> Key: CALCITE-4140
> URL: https://issues.apache.org/jira/browse/CALCITE-4140
> Project: Calcite
> Issue Type: Task
> Affects Versions: avatica-1.17.0, 1.23.0
> Reporter: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.27.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Gradle build cache enables to reuse build artifacts across different build executions: https://docs.gradle.org/current/userguide/build_cache.html
> For instance, if linq4j code is not modified, its `compileJava` and `javadoc` results can be reused in the other builds (e.g. PR builds).
> {{test}} tasks should probably not be cached as the tests often include integrations with databases, so we should execute them from scratch.
> Note: the cache is sensitive to Gradle version, Java version, and extra files in the workspace, so the common practice is to seed the cache only from CI jobs.
> There's ticket for ASF build cache: https://issues.apache.org/jira/browse/INFRA-20516, however, it is likely we won't be able to use it in GitHub Actions :-/
> An alternative option is to setup AWS S3-backed cache via https://github.com/burrunan/gradle-s3-build-cache
> ---
> Note: the remote build cache can be disabled with {{-Ps3.build.cache=false}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)