-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize Gradle builds by enabling local build caching #3718
Conversation
4a9c83b
to
05d4845
Compare
❌ Gradle Check failure 4a9c83ba6a28010cac386f324e60d1405f97424e |
✅ Gradle Check success 05d48456e0b514a35c312155eb8d5bd4839b3fd6 |
@reta could you rebase on main to consume the new gradle check? |
05d4845
to
115f91b
Compare
@peterzhuamazon cryptic failure:
|
115f91b
to
c5b8b76
Compare
Hi @reta I have fixed the issue in #3728 please rebase again. |
Thanks a lot, @peterzhuamazon , no problem at all |
Signed-off-by: Andriy Redko <[email protected]>
c5b8b76
to
8fed6dc
Compare
Interesting that I just triggered a run on main and it passed. |
Flakiness at work ... :( |
Lets give it a minute as I have a new PR incoming to clear up all the opensearch existing processes before using it for another run. Will rebase this PR once that is in. Thanks. |
We public CI we have awesome visibility on the health of the builds: Thanks for that, @peterzhuamazon ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Random question...does ./gradlew clean
also clear this cache?
Thank you!
Aha, good one - nope! That means next build ( fe |
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497)
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497)
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497)
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497) Co-authored-by: Andriy Redko <[email protected]>
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497) Co-authored-by: Andriy Redko <[email protected]>
Signed-off-by: Andriy Redko <[email protected]> (cherry picked from commit e734497) Co-authored-by: Andriy Redko <[email protected]>
…oject#3718) Signed-off-by: Andriy Redko <[email protected]>
Signed-off-by: Andriy Redko [email protected]
Description
The Gradle build cache is a cache mechanism that aims to save time by reusing outputs produced by other builds. The build cache works by storing (locally or remotely) build outputs and allowing builds to fetch these outputs from the cache when it is determined that inputs have not changed, avoiding the expensive work of regenerating them [1].
Even when used by a single developer only, the build cache can be very useful. Gradle’s incremental build feature helps to avoid work that is already done, but once you re-execute a task, any previous results are forgotten. When you are switching branches back and forth, the local results get rebuilt over and over again, even if you are building something that has already been built before. The build cache remembers the earlier build results, and greatly reduces the need to rebuild things when they have already been built locally. [2]
[1] https://docs.gradle.org/current/userguide/build_cache.html
[2] https://docs.gradle.org/current/userguide/build_cache_use_cases.html#use_cases_cache
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.