Short lived develocity key generation causes configuration cache misses

[trevjonez]

The new behavior of always generating a temporary develocity keys should be optional behavior.

Then because the environment variable will never be consistent it leads to perpetual configuration cache misses.

Possibly related issue: gradle/gradle#20873

[bigdaz]

Thanks for reporting. We think short-lived tokens are important for security, which is why they are enabled by default. If possible, we plan on fixing this in the DV Gradle plugin.

You can avoid short-lived tokens in the meantime by passing the DEVELOCITY_ACCESS_KEY environment variable directly to the step that runs Gradle, or configure it for the Job in a Step after the setup-gradle action has run.