This message was deleted.
# develocity
s
This message was deleted.
s
It used to be uploaded correctly, but we recently turned on Android flavors, which created many extra Gradle configurations (that could be the main cause).
n
Hey Simon! Sorry to hear you are having trouble with this. Could you please file a support ticket at support.gradle.com ? A support bundle would also help us diagnose this issue. Here is how you can share a support bundle https://docs.gradle.com/enterprise/helm-admin/current/#support
s
Hi Nelson, I don't think this is related to our Gradle enterprise instance, because it still works, but not for this specific usecase where we probably have too many data (200_000+ configurations). Do you know if there are settings to reduce the content send in the scan? We are not really interested in the specific tasks/configurations data, but more about generic stuff like total duration, memory usage, total dependency size, etc. I probably can take some time to ask my company to give me these details, but I'm pretty sure the answer from the support will be something around the lines of: the gradle scan is too big (which I'm aware of 😛 )
👀 1
n
HI Simon, without more information, like the information in the support bundle, I can only give you speculative answers. In order to give you definitive answers, please file a support ticket! 😄
s
I'll ask my admins if they can share this info, thanks.
n
Yes, feel free to also open the ticket before you have that information!
s
Thanks for the support. The server-side config
ingest.softMaxPayloadSize
was updated, and in the meantime we found out that some modules were not useful to the warmup phase and were disabled, reducing the total Gradle scan size below the initial threshold 👍
n
👍