This message was deleted.
# performance
s
This message was deleted.
c
Does it require credentials? I'm trying to remember because I had issues with that long time ago
Profiler uses its own gradle directory (unless you configure it) so you may need to create a gradle.properties there
i
Thanks for the idea. No credentials required to download, and our build task doesn't try to publish. We do have a gradle.properties in the root of the project with some other settings. Is that ignored by gradle-profiler?
c
I'm talking from memory, my issue was the ~/.gradle/gradle.properties, not the project one
👍 1
i
Shot in the dark I added
--cli
, and gradle-profiler completes successfully now for both benchmarking and profiling my project. Should I file a bug, or is this user error on my part?
😯 1
z
@Ian Brandt I ran into this and as @CristianGM mentioned it uses the Gradle version of your project, which knows nothing of your artifactory config in
gradle-user-home
. If it can't find one it actually creates a local one in your project if I'm not mistaken, but i digress... To resolve this I had to use
--gradle-user-home ~/.gradle/
but interested in what
--cli
actually does. Any more info on that?