Is profiling with --profile broken?


(David Pärsson) #1

I have tried executing

gradle --profile taskName

(where ‘taskName’ is an actual task), using both gradle and the gradle wrapper, for 1.4, 1.5 and 1.6, but no ‘profile’ directory appears in ‘build/reports/’, or anywhere else for that matter.

Am I doing something wrong, or is this broken?


(Peter Niederwieser) #2

That’s strange. It works fine for me with all three versions, and the report can always be found under ‘build/reports/profiles’. Maybe the build output directory has been reconfigured in your case?


(David Pärsson) #3

Thanks. Knowing that it should work, I worked it out.

We have a multi-project setup and it seems the profile reports show up in the build folder of the root project, even when only profiling a sub project.


(Peter Niederwieser) #4

That’s correct. It profiles a whole Gradle invocation, not limited to a particular project.