Hello <#C88E12QH4|detekt> community. A question for Gradle users. I just posted it here, on GitHub d...

# detekt

[gavvvr]

Hello #detekt community. A question for Gradle users. I just posted it here, on GitHub discussions https://github.com/detekt/detekt/discussions/4196.

How do you decouple a failing detekt task from gradle build task graph? I am not ready to fix all my existing code base right now to make this step pass. I would like to exclude it from gradle build and run on demand only, by calling it explicitly with gradle detekt

[Endre Deak]

gradle build -x detekt would skip detekt

[Javier]

What about providing a baseline file?

[Brais Gabin]

Agree, I think that the baseline is the perfect fit for your requirements. This way you just spot the new issues meanwhile you can remove the old ones slowly.

[gavvvr]

@Endre Deak, on GitHub I said that it’s not an option.
Baseline is a good idea, but I haven’t yet decided what rules I would like to use.

So weird that I don’t see an easy way to exclude some intermediate task from tasks graph. In Maven it’s usually a user’s responsibility to tie particular task to Maven phases

[Endre Deak]

sorry I haven’t read it through

[Endre Deak]

how about something like

tasks.withType<DefaultTask> {
    tasks.getByName("detekt").enabled = false
}

[ephemient]

if you applied the plugin normally, the kotlin dsl will provide a generated accessor

tasks.detekt { enabled = false }

or you can disable all detekt tasks

tasks.withType<Detekt>().configureEach { enabled = false }

[ephemient]

if you just want to disable it when running check, that can be done conditionally, e.g.

gradle.taskGraph.whenReady {
    if (hasTask("check")) {
        tasks.detekt { enabled = false }
    }
}

[gavvvr]

Hi @ephemient. Thanks for the tasks.detekt { enabled = false } part! I would like to disable it not on check , but in any case unless detekt task name is explicitly provided to gradle as an argument. I have a solution on my original GitHub discussion (if (!("detekt" in gradle.startParameter.taskNames)) {tasks.detekt { enabled = false }}), but it probably looks ugly

[ephemient]

that works, although at that point I feel you may as well

plugins {
    id("detekt") apply false
}
tasks.register<Detekt>("detekt") {
    ...
}

if you don't want anything wired up by default