Update Gradle Build Cache config to permit read-only access #4296
Conversation
This file contains 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
- Always configure build cache, even if the credentials aren't present. - When on CI, enable pushing to remove build cache, but disable local cache (to force CI to update the remote cache). - Always set the credentials. Even if they're missing, then Gradle should permit read-only access. This will improve build performance for all users.
|
Nice 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This will improve build performance for all users.
Further configuration might be necessary to permit read-only access to the Gradle Build Cache instance, because I can't access https://ktor-gradle-cache.teamcity.com/cache