From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

With the <https://gradle.com/develocity/releases/2025.1#enforced-expiry-date-for-all-access-keys|newly enforced expiration of access keys> in develocity 2025.1, we expect the related error to pop up for our users more regularly.
```Publishing build scan...

The Develocity server (&lt;redacted&gt;) rejected the access key with prefix '&lt;redacted&gt;'.
Your access key has been revoked.```
It doesn't include the suggested fix of rerunning the `provisionDevelocityAccessKey` task, even though that is suggested if no key has been provisioned yet.
Is there any chance this suggestion can be added to the error message?

Hi <@UMG417LGH>, thanks for the feedback. We'll take that into consideration :+1:

Would be really nice if we could ask the plugin to check the credentials before starting the build too

I ended up writing a value source to hit `/api/version` to check them at plugin apply time. But I figure I may not be the only one needing to be more aggressive about credential verification.