You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With configuration enabled, i.e. having the Gradle property org.gradle.configuration-cache set to true, the buildscan profiler does not print the buildscan URL to the console output.
However if the configuration-cache property is set to false the buildscan URL is displayed.
Check also also agains Gradles command line option --scan. There the output shows a buildscan URL independent of the org.gradle.configuration-cache property. That's why I'd assume it is a bug in gradle-profiler.
Steps to reproduce
have an minimal Gradle project (one directory with only one empty file: settings.gradle.kts)
create a gradle.properties file with org.gradle.configuration-cache=true
run gradle-profiler --profile buildscan help
Expected Result
Console output ends with those lines
[...]
Scenario using Gradle 8.6
- Build scan for measured build #1: https://gradle.com/s/<scan-id>
Actual Result
Console output ends with those lines
[...]
Scenario using Gradle 8.6
Environment
Gradle Profiler version 0.20.0
(Latest Homebrew binary, however I can also reproduce it with a build from the latest gradle-profiler master checkout)
Gradle Wrapper used in the minimal sample repo:
------------------------------------------------------------
Gradle 8.6
------------------------------------------------------------
Build time: 2024-02-02 16:47:16 UTC
Revision: d55c486870a0dc6f6278f53d21381396d0741c6e
Kotlin: 1.9.20
Groovy: 3.0.17
Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM: 17.0.10 (Homebrew 17.0.10+0)
OS: Mac OS X 14.4.1 aarch64
The text was updated successfully, but these errors were encountered:
Bug report
With configuration enabled, i.e. having the Gradle property
org.gradle.configuration-cache
set totrue
, the buildscan profiler does not print the buildscan URL to the console output.However if the configuration-cache property is set to
false
the buildscan URL is displayed.Check also also agains Gradles command line option
--scan
. There the output shows a buildscan URL independent of theorg.gradle.configuration-cache
property. That's why I'd assume it is a bug in gradle-profiler.Steps to reproduce
org.gradle.configuration-cache=true
gradle-profiler --profile buildscan help
Expected Result
Console output ends with those lines
Actual Result
Console output ends with those lines
Environment
Gradle Profiler version 0.20.0
(Latest Homebrew binary, however I can also reproduce it with a build from the latest gradle-profiler master checkout)
Gradle Wrapper used in the minimal sample repo:
The text was updated successfully, but these errors were encountered: