The scripts should expose an option to increase the timeout

[bmuschko]

Under certain conditions (e.g. a lot of data, CPU load on Develocity server), uploaded build scans can take a while to fully process. During the last step "Merge build results", the previously-uploaded build scans cannot be retrieved. I believe the retrieval process has a timeout of 10 seconds by default. Allow the end user to provide a custom timeout to work around this issue e.g. via --timeout.

[runningcode]

Hi @bmuschko, does editing connect.timeout or the read.timeout lines in the network.settings file help for this use case or are you asking for something else?

[bmuschko]

Ah, I didn't even notice that file before. Thanks for pointing me to it. That'll do.

[erichaagdev]

There are three timeouts to consider here.

The first two are the connect.timeout and read.timeout. They only control the connect and read timeouts of the underlying OkHttpClient.

https://github.com/gradle/gradle-enterprise-build-validation-scripts/blob/d3f88c728cbac9419a4ce694ade503e005d91879/components/fetch-build-scan-data-cmdline-tool/src/main/java/com/gradle/enterprise/api/client/GradleEnterpriseApiClient.java#L108-L117

The third timeout to consider is the time we wait for the build scans to be available. This is controlled by the availabilityWaitTimeoutSecs query parameter included in the call to the Develocity API. Currently, this value is always hardcoded to 10 seconds and is not configurable. In conditions where Develocity is under load and there is a delay in build scan processing you could encounter the issue you're describing.

To say this differently, regardless of the values of connect.timeout or read.timeout, the scripts will only ever wait for a maximum of 10 seconds for the build scans to ingest.

I think this is a valid issue and will reopen it.