Hi Lukasz!
Thanks for reporting this. It’s caused by the spotless plugin resolving build script configurations in an unexpected place, which is why removing spotless from your build fixes the issue.
We will include a fix to handle the unexpected data more gracefully in the next version of Gradle Enterprise and will of course update scans.gradle.com when the fix is available.
In the meantime your options are to remove spotless as you have done here, or downgrade the build scan plugin to version 2.3. The latter means that you won’t collect / view the new dependency data that 2.4 enables, but it also won’t fall over before the bug is fixed.
Hope that helps!
Regards
Tom