[CALCITE-4140] Add Gradle Remote Build Cache configuration#2081
Closed
vlsi wants to merge 1 commit intoapache:masterfrom
Closed
[CALCITE-4140] Add Gradle Remote Build Cache configuration#2081vlsi wants to merge 1 commit intoapache:masterfrom
vlsi wants to merge 1 commit intoapache:masterfrom
Conversation
vlsi
force-pushed
the
build_cache
branch
6 times, most recently
from
576d3fd to
0d3910c
Compare
danny0405
reviewed
Jul 27, 2020
vlsi
force-pushed
the
build_cache
branch
7 times, most recently
from
210ed72 to
96a26d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See https://issues.apache.org/jira/browse/CALCITE-4140
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
compileJavaandjavadocresults can be reused in the other builds (e.g. PR builds).testtasks 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