FYI scans.gradle.com will be undergoing maintenance shortly and will be unavailable for 60-90mins. See status.gradle.com for current status.

Done, service resumed.

Hi, I'm wondering if there is a flag to enable test output on successful execution? I'm looking in the test section of a successful build scan I can see the below message so I'm wondering if this can be overridden to output even on a successful execution of a test suite.

Test output is not captured for successful test executions, except for the first successful retry after a prior failure

Thanks in advance, Connel

Hi, is it possible to export Gradle Ent build scan to a CVE file (or otherwise download somehow) , we are running some custom experiments and wish to collate some data not easily accessible on dashboards when looking at a collection of data, specifically interested in collating some data sets of tasks comparing against the types of machines local devs are using (number of cores etc)

Hi, we want to restrict running specific tasks if there is no authorisation with Gradle Enterprise (and remote cache GE built-in node). Is there any API to check that ~/.gradle/enterprise/keys.properties contains a valid token?

Hi, is there a way to know whether configuration cache was re-used in a build with the GE API?

Hi, Using Gradle Enterprise Maven Extension ver 1.16.2. In a build that includes Lombok on the classpath I get this combination of printouts in the log. [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ project-name --- [WARNING] The following annotation processors were found on the classpath: [lombok.launch.AnnotationProcessorHider$AnnotationProcessor, lombok.launch.AnnotationProcessorHider$ClaimingProcessor].Compile avoidance has been deactivated. Please use the <annotationProcessorPaths> configuration element of the compiler plugin to declare the processors instead.If you did not intend to use the processors above (e.g. they were leaked by a dependency), you can use the <proc>none</proc> option to disable annotation processing.For more information see https://gradle.com/enterprise/help/maven-extension-compile-avoidance. [INFO] Loaded from the build cache, saving 0.337s Isn't that a bit strange? Contradiction? I get the same log whether the <annotationProcessorPaths> configuration is added or not.

Q: Are there any plans to add filter support to the

/api/builds

endpoint? It is extremely expensive to filter on the client side and does not scale well for installations with many builds.

hello, cross-posting from #caching - https://gradle-community.slack.com/archives/CA83B1VLL/p1676490224535769

Hi all, I'm frequently getting errors from remote build cache node:

response status 502: Bad Gateway

. It happens on local machines as well as CI agents. Build Cache Node version is 12.2. Is there anything I can do to fix this?

In gradle buildscans, is there any indication that a gradle toolchain is being used when doing builds? The infrastructure info only shows the Java version used to run Gradle.

Can build scans be used to figure out why two builds are unable to share the same daemon?

Hello, do we have a build-scan tag when build-cache had failures during build? Maybe in some custom data plugin? If no, how can this information can be extracted?

Hi all 👋 Can I see the command line that was used to trigger my build in build scans? It says here that it's captured but I can't find it anywhere 🕵️

Hi all, we have few developers that get super super slow build, culprit is this issue (we’re not sure what exactly cause it, Kotlin 1.7.20) :

Could not perform incremental compilation: Could not connect to Kotlin compile daemon                 
Could not connect to kotlin daemon. Using fallback strategy.

For monitoring purpose is there a way to tag a build in the build scan when such issue happen? (we don’t store build logs in GE)

Hello. I tried to perform android instrumentation tests with Gradle Managed Devices source code : https://github.com/ganadist/VersionCodeDemo/tree/gmd_test And when tests are performed, gradle scan does not show test result. https://scans.gradle.com/s/t25tqkwsikulk/tests/overview Is it known issue? and is there a plan to support for android instrumentation tests?

❓ Hey folks, does Gradle Enterprise support identifying users of a particular dependency across all onboarded projects? For example, if I wanted to know which projects in my organization are using JUnit 5.9.1, could Gradle Enterprise help me answer this? The data should be there via build scans, shouldn't it?

This channel might be better suited for this question. Cross posting for higher visibility.

Hi, I’d like configure a rule to only publish when there is a

CI

tag. However, this example shows a

CI

environment variable https://docs.gradle.com/enterprise/maven-extension/#publishing_based_on_criteria. Is there a way to look at tags passed via

<http://scan.tag.ci|scan.tag.ci>?

If I have two build scans open in a GE instance. Is there some way to diff exactly these two build scans I don't see? The only way I see is to press "compare" on one and then try to find the other build scan via the search which might be pretty hard unless you have some unique value per build as custom value.

Hi, I have a GE issue. when opening the GE via a browser but also from local build scans GE redirects to

/starting/

. It has been like this for ~2 hours. We are using the Helm installation. In the developer tools console in the browser there is the following error:

arting.js:22 Caught checking readiness TypeError: Failed to fetch
    at check (starting.js:27:5)

hi folks, i am trying to setup gradle build scans for an open source project that uses maven. • https://github.com/FluentLenium/FluentLenium/pull/1852 This is a maven multi module project. It uses different test frameworks (junit4, junit5, testng, spock and kotest) in its modules. I am running into some issues when trying to add the gradle enterprise extension. Apparently there are some issues with a module that uses testng (see stacktrace below). Is this a known issue/limitation of the extension?

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0:test (default-test) on project fluentlenium-spring-testng:
[ERROR]
[ERROR] Please refer to /Users/abendt/IdeaProjects/FluentLenium/fluentlenium-spring-testng/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] There was an error in the forked process
[ERROR] Cannot invoke "com.gradle.maven.scan.extension.test.listener.testng.a.a()" because "<parameter1>" is null
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
[ERROR] Cannot invoke "com.gradle.maven.scan.extension.test.listener.testng.a.a()" because "<parameter1>" is null
[ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:631)
[ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:285)
[ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:250)
[ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1203)
[ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1055)
[ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:871)
[ERROR] 	at com.gradle.maven.cache.extension.d.c.a(SourceFile:26)
[ERROR] 	at com.gradle.maven.cache.extension.d.n.a(SourceFile:23)
[ERROR] 	at com.gradle.maven.cache.extension.d.h.a(SourceFile:28)
[ERROR] 	at com.gradle.maven.cache.extension.d.m.a(SourceFile:27)
[ERROR] 	at com.gradle.maven.cache.extension.d.a.c(SourceFile:115)
[ERROR] 	at com.gradle.maven.cache.extension.d.a.a(SourceFile:61)
[ERROR] 	at com.gradle.maven.cache.extension.d.e.a(SourceFile:27)
[ERROR] 	at com.gradle.maven.cache.extension.d.l.a(SourceFile:17)
[ERROR] 	at com.gradle.maven.cache.extension.d.d.a(SourceFile:42)
[ERROR] 	at com.gradle.maven.cache.extension.d.b.a(SourceFile:26)
[ERROR] 	at com.gradle.maven.cache.extension.d.f$1.run(SourceFile:35)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(SourceFile:29)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(SourceFile:26)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(SourceFile:66)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(SourceFile:59)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(SourceFile:157)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(SourceFile:59)
[ERROR] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(SourceFile:47)
[ERROR] 	at com.gradle.maven.cache.extension.d.f.a(SourceFile:31)
[ERROR] 	at com.gradle.maven.cache.extension.d.k.a(SourceFile:65)
[ERROR] 	at com.gradle.maven.cache.extension.h.b.lambda$createProxy$0(SourceFile:65)
[ERROR] 	at jdk.proxy9/jdk.proxy9.$Proxy72.execute(Unknown Source)
[ERROR] 	at com.gradle.maven.scan.extension.internal.d.a.executeMojo(SourceFile:114)
[ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:342)

We just bumped to latest GE 2023.1.1 and we are getting many timeout errors when trying to submit build scans (still using plugin 3.12.3)

'java.net.SocketTimeoutException: Read timed out'

It is happening both locally and in CI. It’s hard to quantify the error rate, but locally it failed to me half of the times in 6 consecutive builds, and in CI I just finished a job with four different gradle executions and wasn’t able to publish any scan. Is there any change in the timeout configuration in latest version? Can we edit this somehow? Is anyone else having this?

Hi there Gradle Enterprise Community! 🙂 Pinning a notice here on the best way to receive support for Gradle Enterprise. We use Zendesk for support issues. This provides the fastest and best experience, and has escalations built in based on severity. If you are experiencing an issue affecting Gradle Enterprise functionality, please file a ticket. You can file a ticket here: https://support.gradle.com/hc/en-us

Feature request: would like to configure the GE plugin to avoid sending the console output if the gradle build is successful. Would be a nice way to save space on the GE server...

Hi, When upgrading failsafe-maven-plugin to latest version (3.0.0) in my build I get the attached message that caching was disabled. I suppose I could add some custom configuration, but according to documentation Gradle Enterprise Maven Extension should support failsafe-mave-plugin out of the box. I think this might be a regression.

Hi, I am curious if Gradle Enterprise knows about the new Bitrise offering for remote cache and management as SaaS product. I don't know if they can do the scan comparison but cache usage metrics, alerts and global cdn distribution looks nice. Is there any plan for GE SaaS and a custom alerting solution?

Hi, someone who can help me fix this error.

Hello, someone who can help me fix this error. [3:12 AM] Having problem in my flutter project Exception in thread "main" java.io.FileNotFoundException: https://downloads.gradle.org/distributions/gradle-7.3.0-all.zip at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1993) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) at org.gradle.wrapper.Download.downloadInternal(Download.java:58) at org.gradle.wrapper.Download.download(Download.java:44) at org.gradle.wrapper.Install$1.call(Install.java:61) at org.gradle.wrapper.Install$1.call(Install.java:48) at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65) at org.gradle.wrapper.Install.createDist(Install.java:48) at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:128) at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

Hi, I'm trying to upgrade Gradle Enterprise from 2022.4.7 to 2023.1.x, and when using any version bigger than 2023.1.1, I'm unable to log in using Okta. It doesn't matter if I go 2022.4.7 -> 2023.1.4 (initial try) or 2023.1.1 -> 2023.1.2 (latest try, after 2022.4.7 -> 2023.1.1 was a success). Internal admin account is working, so I can confirm we are on a requested version, and Okta settings are still present, but any time I try to use Okta login, I got

Invalid requester

error... Is this a known issue I just failed to spot in documentation/release notes?