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

Gradle Community

Hey folks,

FYI looks like Cloudflare is down, which is impacting <http://plugins.gradle.org|plugins.gradle.org>.

• <https://www.cloudflarestatus.com/>

Does that also (still) affect submitting build scans?
If I use `--scan` I do not get any output about a created build scan.
If I use `buildScanPublishPrevious` it fails with "Publishing failed. Please consult the task output." which does not help at all, as the task did not output anything. :confused:

`--debug` output claims `<http://scans-in.gradle.com|scans-in.gradle.com>` answered with `200 OK` in both cases though

Hi <@URQ797WRW>, I'm looking into this and everything should be back and operating like normal
But if you're able to provide me with `X-Request-Id` I can find the specifics of what's going on. The request ID should show on the line above the response when you have `--debug` enabled

You can send me the ID in a DM or in this thread

```2025-12-05T13:40:40.118+0100 [DEBUG] [sun.net.www.protocol.http.HttpURLConnection] sun.net.www.MessageHeader@7612c26810 pairs: {GET /usage/users/check HTTP/1.1: null}{X-Request-Id: 6ca9b4eb-a287-4b42-b6bb-eb213b27ade0}{Accept-Encoding: gzip}{X-Gradle-Client-Descriptor: Develocity Gradle Plugin/4.2.2}{Cache-Control: no-cache}{Pragma: no-cache}{User-Agent: Java/17.0.3}{Host: <http://scans-in.gradle.com|scans-in.gradle.com>}{Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2}{Connection: close}
2025-12-05T13:40:40.252+0100 [DEBUG] [sun.net.www.protocol.http.HttpURLConnection] sun.net.www.MessageHeader@6e9befc18 pairs: {null: HTTP/1.1 200 OK}{Date: Fri, 05 Dec 2025 12:40:40 GMT}{Content-Type: application/vnd.gradle.user-count-check-response+json}{Transfer-Encoding: chunked}{Connection: close}{CF-RAY: 9a939d02dda3e0cb-MUC}{cache-control: no-cache, no-store, must-revalidate}{pragma: no-cache}{expires: 0}{x-content-type-options: nosniff}{x-frame-options: deny}{strict-transport-security: max-age=31536000; includeSubDomains; preload}{x-xss-protection: 1; mode=block}{content-encoding: gzip}{X-Proxy-Cache: MISS}{vary: accept-encoding}{cf-cache-status: DYNAMIC}{Server: cloudflare}```

This was now with `gradle help --scan -d` and Develocity plugin 4.2.2 applied

Argh, it is not a server-side issue.
If I run it from terminal it works fine and asks me whether I agree to the ToS.
But if I run it through IntelliJ Gradle integration, no question is asked but simply "no" assumed

And if I apply Develocity plugin 3.19.2 instead of 4.2.2 it also works fine from IJ integration

So this seems to be a problem in the Develocity plugin

That simplifies the troubleshooting a lot, thank you, I was getting a bit worried in regards to how nothing looked incorrect from the server's perspective :sweat_smile:
I'll tag in another colleague internally