[GH] (pekko): Workflow run "Scalafmt" is working again!

[GitBox <gi...@apache.org>]

The GitHub Actions job "Scalafmt" on pekko.git has succeeded.
Run started by GitHub user clayburn (triggered by pjfanning).

Head commit for run:
ece0b84b0928a0bf7f205f51493a0025335e0bb8 / Mirco Dotta <md...@gradle.com>
Disabled Develocity local build cache

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).

Report URL: https://github.com/apache/pekko/actions/runs/11130843998

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org