is there a way to get a stack dump on the deprecat...
# develocity
t
is there a way to get a stack dump on the deprecated buildScan usages? I suspect it is the kotlin plugin + AGP making the calls but not sure how to confirm.
g
I have same issue. Also, this deprecation is not displayed on https://develocity.site/s/xxxx/deprecations page.
p
Unfortunately, there is no easy way to figure this out. I'll check if we can add something in the next patch release of
3.17
. Do you use the Common Custom User Data Gradle plugin? It is one of the common conventions plugins that can produce such warnings.
t
yeah I do but got that update in already. assuming they fixed all the consumption points already anyway
p
If you updated to
2.0+
, then all of them should be gone. Ok, we'll add something in the next patch release to make this investigation easier.
❤️ 1
j
protip for folks migrating from gradleEnterprise to develocity plugin, find uses of the deprecated GE apis by putting breakpoints inside
com.gradle.enterprise.gradleplugin.internal.extension.b
for various methods like
value()
or
tag()
and debugging a build to see what is adding custom metadata under the old apis. I found a weird case where I had
buildScan { }
DSL in a build.gradle file which was not wrapped in
gradleEnterprise { }
or
develocity { }
.
p
Printing the origin of the deprecation is now available in 3.17.3 released today. If you run a build with
-Ddevelocity.deprecation.captureOrigin=true
, for each deprecation we would print a couple of lines that should help you find the origin of the deprecated usage. If those don't help, then add
-Ddevelocity.deprecation.displayFullStackTrace=true
to see the entire stacktrace, which is not shown by default as it is too verbose.
👍 3
👍🏻 1
t
beautiful.
🙌 2
🙌🏻 1