Tracing Gradle task execution For CI builds, I tend to want something more granular than --profile but I don't like the idea of sending details of every build to Gradle with --scan . For now, having the Chrome trace run on CI gives a good picture of how the build is performing and then Java Flight Recorder can be used either manually or with the Gradle profiler to dig into individual task performance.