This message was deleted.
# develocity
s
This message was deleted.
n
Hi Ken, do you mean: a) do not print the build scan link at the end of the build when a build is successful but still upload? b) do not publish a build scan scan for a successful build?
d
I think he means that the build scan shouldn’t include the console output, if the build is successful. Presumably the console output is a hefty part of the memory required in the GE database, but I think that should be measured.
☝️ 1
n
Thanks for clarifying, David, I understand now. You can configure whether build logs and test logs are captured in general for builds cans. https://docs.gradle.com/enterprise/gradle-plugin/#capturing_build_and_test_outputs Test logs are only captured for successful tests, but this is a good point about the console log output only for successful builds.
k
yep...would like to disable console log output for successful builds 👍
We use gradle for backend builds as well, so console logs are decent amount of space on the GE server and in most cases it's not needed, so we disable by default here. If the build fails though, it'd be nice if the console output were included so we can debug what happened on a user's system more easily (we currently ask them to turn on output via a ~/.gradle/gradle.properties setting when we need it)
n
I see. Have you considered moving your build scan storage to s3 for cheaper storage?
k
that I'm not sure about (was a decision that predates me)...trying to work around our default while still being able to easily help devs easily...