Cross-posting here: https://gradle-community.slack.com/archives/CAHSN3LDN/p1736262758991409?thread_ts=1736260845.634329&cid=CAHSN3LDN

👋 Just getting started with problems api. Was wondering the scope it, can it be used to catch any errors thrown during the build by any task.

Hey guys, I'm excited to look into Clean and actionable reporting for Gradle code quality plugins for Kotlin project in GSoC 2025 chapter, is there any related discussions or issues to learn more about this proposal? thanks!

Hello, I've been trying to integrate the Problems API into a simple gradle plugin project but I'm having some issues. I use the ProblemReporter to report problems in a particular task, when I run the task, I get the html problems report but I don't see the reported problems in IntelliJ, is that expected behaviour? I was under the assumption that clients of the Tooling API like IDEs will pick up the reported problems and do something with them, in this case I thought IntelliJ would show the reported problems in the Problems tab or something

Hi, I was in the general Kotlin slack and am interested in the Clean and Actionable reporting for Gradle code quality plugins for Kotlin. I already wrote up my proposal and would like some early feedback if possible! I will reply in thread with my doc.

Hi @Vanessa Johnson! Welcome to Google Summer of Code, and looking forward to working with you together with @Reinhold Degenfellner @Donát Csikós and hopefully a few other contributors! How is your availability in the coming 2 weeks during the community bonding? It would be nice to schedule a first team meeting so that we could align on the communication channels and the first steps for the coding phase

So, notes from the call: 1. We start from Problems API in the Detekt Plugin, as per proposal 2. Good first steps: a. Update the project page b. Create GitHub issue(s) for the first deliverables c. Create meeting invites / docs for meeting notes d. Try building Detekt plugin and the repo locally so that there are no surprises 3. Scope for the first patch: ◦ Feature itself - as in the project proposal ◦ Test coverage - some roundtrip test for Problems API would be useful ◦ Nice2have: Documentation - if we have special use requirements ◦ Some demonstration of things working - Currently we have only HTML report as a consumer, but there is ongoing work on CLI and some opportunities for GitHub Checks CC @Vanessa Johnson @Donát Csikós @Reinhold Degenfellner - let me know if I missed something

Hi! I'm interested in creating a plugin to export the Problems API to GitLab's merge request UI. I've already created a few plugins and I'm familiar with the GitLab format, so that shouldn't be a problem. Ideally, this would take the form of a Gradle (settings?) plugin that when applied, listens to all emitted problems, and at the end of the build generates the JSON report expected by GitLab. However, I don't understand how a Gradle plugin can access the reported errors. The documentation mentions:

Tooling API clients can access detailed problem reports associated with build failures via the

Failure

object on the root build operation. To receive these reports, the clients must register a progress listener for the

OperationType.ROOT

operation type. The progress listener callback should then check if the operation result is of type

FailureResult

, and then it can access the associated problems via

Failure.getProblems()

.

However, this only applies to those using the Tooling API, whereas my project would be a Gradle plugin itself. How can I access the reported problems from a Gradle plugin? For convenience (to avoid having it to be declared in each project), it would be better if I could access the reported problems directly from a settings plugin.

Hi @Oleg Nenashev @Donát Csikós @Reinhold Degenfellner , I don’t think our meeting today is necessary but I do have some follow up questions that I’ll put in this thread 🧵

Thanks! Also do I need any specific permissions to push to the repo? I was having some issues pushing up my branch yesterday but it could really be on my end too. Sorry for the late message. I just send this message in the channel and not in the thread

@Vanessa Johnson https://github.com/detekt/detekt/blob/main/detekt-gradle-plugin/src/functionalTest/kotlin/dev/detekt/gradle/plugin/DetektBasePluginSpec.kt - for smoke test example

@Vanessa Johnson did you have a chance to create your first pull request?

FWIW I am on vacation but can join the call if needed. It is better to discuss on the chat though

@Oleg Nenashev @Reinhold Degenfellner I’m running into this error I haven’t been able to fix. I’ve tried a few potential solutions but that doesn’t seem to be the way to go because I would no longer see the “Incubating” line. Pictures will be in 🧵

I will be a few minutes late to the meeting

@Vanessa Johnson @Reinhold Degenfellner FYI, here is the recordifng of the demo from Friday. I have not processed it yet beyond a few minor tweaks, and feedback is welcome - https://drive.google.com/file/d/1Eulmey166Whm5me3lq7C0IlywSgT5ubr/view?usp=drive_link

@Vanessa Johnson @Reinhold Degenfellner my apologies, I somehow missed the meeting today. I thought it is at 15:00 my time, but it was an hour earlier. Did you meet?

@Oleg Nenashev @Reinhold Degenfellner Is it possible to still join the Gradle tool newsletter for the August CFP? When does that usually close?

@Vanessa Johnson https://github.com/detekt/detekt/issues/7454 - old ticket FYI

Hi @Oleg Nenashev @Reinhold Degenfellner I have a PR up for Ktlint in 🧵 .

@Vanessa Johnson @Reinhold Degenfellner I'm so sorry, but I cannot join today. I am at the conference, and I had to prioritize some administrative stuff at work

@Oleg Nenashev Hey, I know @Reinhold Degenfellner is on vacation. Do you have time to meet today? If not we can do it async

@Vanessa Johnson some notes about https://dev.to/gradle-community/enhanced-kotlin-code-quality-reporting-with-the-gradle-problems-api-56bo • It would be nice to add tags so that the post is discoverable • Kotlin logo is an old one, it makes sense to update • It would be nice to promote the post on #CRA9GTYBH. There is also a newsletter CFP - https://community.gradle.org/contributing/spread-the-word/

@Vanessa Johnson ✅ reviews from the maintainers are in

Hi all! I’ve been working with GSOC to integrate the Gradle problems API into Ktlint & Detekt. Free feel to take a look at the linked PRs (work in progresses). I would say Ktlint is closer to being merged in! I’ll have a follow up about Ktlint in the coming days! This is the project page if you want to read a little more about the problems api!

@Vanessa Johnson FYI https://github.com/orgs/community/discussions/26254 for the issue with pushing to the repo and workflow changes

@Oleg Nenashev @Reinhold Degenfellner Good Morning, can we push our meeting back a hour? To 9AM EST and I think 3pm your time?

@Vanessa Johnson how is it going with the PRs? Do we have a hope of merging them before Sep 1 submission deadline? • New PR is pending: https://github.com/detekt/detekt/pull/8562 • PR pending, I pinged Jonathan: https://github.com/JLLeitschuh/ktlint-gradle/pull/927 • There was no patch to https://github.com/pinterest/ktlint afterall

@Oleg Nenashev @Reinhold Degenfellner when doing the final submission is it fine to include the project page as the link since I need to show multiple links for the work?

@Oleg Nenashev I cherry-picked but it won’t push to the old branch. Picture in 🧵