-
Notifications
You must be signed in to change notification settings - Fork 282
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
Reenable gradle build cache #3185
Comments
…ndency is used We suspect that we are seeing the snapshot build of opensearch be cached in some circumstances and not cached in others that is creating a mix of build failures that are hard to interpret. Follow up issue to revisit and potentially renable this setting opensearch-project#3185 Signed-off-by: Peter Nied <[email protected]>
…ependencies (#3186) Disable gradlew build cache to ensure most up-to-date dependencies We suspect that we are seeing the snapshot build of opensearch be cached in some circumstances and not cached in others that is creating a mix of build failures that are hard to interpret. Follow up issue to revisit and potentially renable this setting #3185 Signed-off-by: Peter Nied <[email protected]>
…t up-to-date dependencies Backport 5e8f12c from opensearch-project#3186. Disable gradlew build cache to ensure most up-to-date dependencies We suspect that we are seeing the snapshot build of opensearch be cached in some circumstances and not cached in others that is creating a mix of build failures that are hard to interpret. Follow up issue to revisit and potentially renable this setting opensearch-project#3185 Signed-off-by: Peter Nied <[email protected]> (cherry picked from commit 5e8f12c)
…t up-to-date dependencies (#3187) Backport 5e8f12c from #3186. Disable gradlew build cache to ensure most up-to-date dependencies We suspect that we are seeing the snapshot build of opensearch be cached in some circumstances and not cached in others that is creating a mix of build failures that are hard to interpret. Follow up issue to revisit and potentially renable this setting #3185 Signed-off-by: Peter Nied <[email protected]> (cherry picked from commit 5e8f12c)
With the cache disabled we will see more failures due to intermittent network issues when downloading dependencies. It might be a good idea to support at least for some level of dependencies
|
Looks like downloading the gradle distro got interrupted and failed a run
|
[Triage] Hi @peternied, thank you for filing this issue. Based on the info you provided, I am marking this issue as triaged with the two tasks required for closure being determining the best way to handle the caching and then actually do that. |
Seems like this is a good solution for enabling gradle build cache: https://github.com/marketplace/actions/gradle-cache i will raise a PR soon. |
Closing this as CI is pretty fast without enabling cache. (comment) |
Feel free to re-open if this still needs to be addressed |
The gradle build cache is used between github actions to speed up build times, but if the wrong cache sources are being used this can result in unexpected failures that are hard to troubleshoot.
We are disabling the remote gradle cache to while stabilizing the build infrastructure. We should revisit what the impact of not having this cache.
Task 1: Determine the best path forward for re-enabling the build cache. Should we re-instate it the same way or in a different way?
Task 2: Re-enable cache in best way.
The text was updated successfully, but these errors were encountered: