[question] (no error) Good afternoon community, I follow quite closely the latest news of Gradle and the initiative to improve the development experience. I work under a hexagonal architecture with several services which have more than 500 integration tests, unit tests, code quality check, etcetera. The build stage on many of these services is quite long and the wait is torture (I have seen build stages of over 1 hour). Do you have any recommendations to start trying to mitigate these monstrous builds? I'd like to be able to take the lead on this but don't quite know where to start. The version we have upgraded services to after a migration is a:

Gradle 8.5

I would very much appreciate any feedback either to route this thread to another channel and/or some documentation or experience from the community.

So if you are doing a full rebuild or --rerun-tasks it will take however long takes to do your build. If you are using gradles up to date checks, build cache and configuration cache things may finish almost in an instant. In our project doing a clean build and rerunning all tests takes multiple hours, but incrementally building/updating an application in a working copy takes less than a second. It's a bit unclear how your build stages currently work. For example if service a gets updated and service b depends on service a, do you run integration test on service a before building b?