What would the best understanding bottle necks of the tasks without Develocity. Scan, check biggest times and reason?

You could try to get information from

--profile

or the

gradle-profiler

, but the information is probably not as accessible as with Develocity or a build scan.

Let me try at least

ninja publish a scan to the public scans server and then delete it after you've reviewed it?