This message was deleted.

Hi @Ken Yee Tagging after publishing is something that was already requested. I’ll relay internally your use case, which will help when prioritizing features. Regarding deleting a build scan after it has been uploaded, it is possible with some admin commands. Please open a support ticket and someone will assist you in doing so.

That’s really interesting @François Guillot, I didn’t know this was possible! Is there any chance to get that documented, so there is no need to ask for support in case we require that?

We didn’t document it because it’s not self-served. You need to execute a query on your database to delete builds (except for scans.gradle.com where you can do that in the UI). I’ll discuss internally whether we want to mention this or not and update the relevant documentation.

Thanks.. On a separate note..is there any way to automatically detect that a build time included laptop hibernate time? I.e. can the Gradle daemon detect this?

In the meantime, is there a way for us to do this by executing a query against the backing DB or something? We’re trying to leverage the gradle enterprise dashboards to track our metrics, but can’t do this without being able to either: • retroactively tag a build • exclude a build by ID in the query • delete a build (preferably not this) Maybe there’s another potential workaround?

There is no other workaround I’m afraid, except deleting it.