This message was deleted.
# community-support
s
This message was deleted.
c
Start by running a build scan and analyze that
v
Also you can try investigating using the gradle-profiler: https://github.com/gradle/gradle-profiler Btw., if you add `dependsOn`s, it is more a sign that something else is wrong. Practically any
dependsOn
that does not have a lifecycle task on the left-hand side is a code smell and it's most often a sign that you do not properly wire task outputs to task inputs where you get necessary task dependencies automatically.
a
That would be interesting to know what got slower. One idea is, that Gradle 8 probably consumes more memory, so maybe adding more memory could help. But maybe you could use build scan as suggested and see what part takes the most of the time and got slower. Since 2h is a long build, maybe it's just that tests are slower for some reason (upgraded test library?)