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.
Enables remote Gradle cache on S3, closes #490
First, S3 bucket permissions should be rechecked based on https://github.com/burrunan/gradle-s3-build-cache#s3-bucket-permissions-for-cache-population. Cache should be readable for everybody, without credentials. In order to write to cache, we have to provide credentials. Plugin does require its own pair of env variables (not to mess with default configs locally). GHA populate them from secrets, which are available only on master branch. This is automatically guarantee that only nighty build on master can populate cache. And all other builds, including local on developers machines, can read that cache.
This is complimentary to GHA Gradle cache that we already have. Both will do their part to, hopefully, reduce our build times .