Disable Develocity local build cache #1512
Merged
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
clayburn
changed the title
pjfanning
reviewed
Oct 1, 2024
project/PekkoDevelocityPlugin.scala
Outdated
| } | ||
| // See https://docs.gradle.com/develocity/sbt-plugin/#enabling_build_cache_in_a_custom_sbt_configuration | ||
| override lazy val projectSettings = DevelocityPlugin.develocitySettings(Jdk9.TestJdk9) | ||
| } |
There was a problem hiding this comment.
minor nit but could you add a new line at the end of the file?
sbt-develocity v1.1 ships with local and remote build cache support for the `compile` and `test` tasks (see https://gradle.com/develocity/releases/2024.2#build-caching-for-sbt). The local build cache is enabled by default, while the remote cache requires configuring the nodes that are allowed to upload artifacts to the build cache (see https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization). It's important to confirm that a project's build is ready to use the build cache (local or remote) to avoid unexpected behaviors. Specifically, one should make sure that all relevant inputs to the `compile` or `test` task are captured, as otherwise the generated build cache key will be incorrect (this can lead to erractic behavior, as entries from the cache will be reused when they shouldn't). Refer to https://docs.gradle.com/enterprise/sbt-plugin/#caching_the_compile_task to know what are the build cache inputs captured for the `compile` task and https://docs.gradle.com/enterprise/sbt-plugin/#caching_the_test_testonly_and_testquick_tasks for the `test` task. This commits disables the local build cache so that a proper rollout can be planned (see https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization).
clayburn
force-pushed
the
disable-local-develocity-build-cache
branch
from
d1d76f5
to
ece0b84
Compare
raboof
approved these changes
Oct 2, 2024
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.
sbt-develocity v1.1 ships with local and remote build cache support for the
compileandtesttasks (seehttps://gradle.com/develocity/releases/2024.2#build-caching-for-sbt).
The local build cache is enabled by default, while the remote cache requires configuring the nodes that are allowed to upload artifacts to the build cache (see
https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization).
It's important to confirm that a project's build is ready to use the build cache (local or remote) to avoid unexpected behaviors. Specifically, one should make sure that all relevant inputs to the
compileortesttask are captured, as otherwise the generated build cache key will be incorrect (this can lead to erractic behavior, as entries from the cache will be reused when they shouldn't). Refer tohttps://docs.gradle.com/enterprise/sbt-plugin/#caching_the_compile_task to know what are the build cache inputs captured for the
compiletask and https://docs.gradle.com/enterprise/sbt-plugin/#caching_the_test_testonly_and_testquick_tasks for thetesttask.This commits disables the local build cache so that a proper rollout can be planned (see
https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization).