just going through the 3.17 migration, curious, th...
# develocity
f
just going through the 3.17 migration, curious, the deprecations don’t seem to flow through to the build scan deprecation tab => no easy way to collate this information across many repos without parsing log lines 😞 is there another way to get this information? Aware that at some point it will start breaking and we want to get ahead of it.
p
Hi Felix, unfortunately, logs are the only place where we capture deprecation warnings. This was a conscious decision to not display them in the "Deprecations" tab.
f
Oh, interesting! Curious, what’s the rationale behind the decision?
p
The main reason was that the "Deprecations" tab exists only in Gradle Build Scans. It is not uncommon for Develocity customers to publish scans for multiple build tools. Since we could not provide the same level of deprecation presence in the timeline we had, we decided to go with a solution that worked for all build tools in the first pass.
I also made a note of your request and will bring it up with the team. We may reconsider this for a future patch release.
f
Oh interesting, I didn’t realise this was now a sink for multiple build tools. Thought it was more of a branding rename. But good to know! Is there no way of conditionally adding to the gradle build scan portion? I’m on a build team trying to migrate this for a large number of repos (>500 😭 ) and it has been easier to process things in bulk from the deprecations tab. I should have the majority covered, but it’s hard to catch some of the outliers especially if my code search doesn’t catch it either.
Ah ok, perfect 👌
Thanks Pavlo!
p
Is there no way of conditionally adding to the gradle build scan portion
I'll check what we can do. How would you use the "Deprecations" tab for this purpose? Would you just pick the latest builds for all repos and check the tab? Or do you use the deprecations API (ref)?
f
sorry had a meeting. I had not seen the API! We had a pipeline in place a while back that was ingesting build scan data dumped in s3. Which upon further inspection seems equivalent-ish to the existing export api? As we’re doing the gradle 8 migration, we’re able to collect data on things we need to solve at the platform level vs bespoke things in peoples repositories. This pipeline was set up a long time ago, and haven’t really revisited the different ways to get data out i.e. export api or the new api.
p
Got it, thank you for explaining.
f
A general point, the build scans have been invaluable for debugging build performance. I’m curious whether you have anything (available or in the works) to better aid platform teams where you can get a holistic view over builds? Also curious to know whether you’ve received any requests for such functionality? Granted it’s a bit vague, but deprecations/migrations/errors that we have to run down across repositories/builds is probably the most actionable example of this.
p
I think the "Develocity Reporting Kit" introduced in 2024.1 could address some of the cases you described (docs). This allows you to export build data and create arbitrary reports. So, you, as a platform team, could create dashboards showing the state of the builds across all repos. I am not an expert in this area, so I don't know what build data is currently available for visualization. We try to cover the gaps in available data in every release, though. If you are interested, I suggest contacting our support or your point of contact for more details on how to set this up.
f
oh that’s really interesting, I’ll have a look and play around with that
thanks!
p
You are welcome 🙂