I have my

checkDebug

lifecycle task In root build.gradle I define

def checkDebug = tasks.register("checkDebug") {
    group = "verification"
}

subprojects { subproject ->
    subproject.pluginManager.withPlugin("com.android.library") {
        tasks.named("checkDebug") {
            dependsOn("${subproject.path}:lintDebug")
            dependsOn("${subproject.path}:testDebugUnitTest")
        }
    }
}

How would I push this into convention plugin? Convention plugin is applied to each project, but there is no central place, so where do I register

checkDebug

once? Or is that not the way? If I register it in every project, it will be availabel to the CLI, but I wont be able to depend on it, so I cannot have my

buildAll

etc, which kills further composing, which is dumb What the idiomatic way of doing this with convention plugins?

What you have is not idiomatic either, as you each into the subprojects model. Latest when you read to use isolated projects or would fail. What you for example could do is to have the task in each project using the convention plugin and then in the root project (it wherever you want) have one task that depends on all those via string-dependency similar to what you have

but that means many

tasks.register("checkDebug")

, right? isnt that somehow less performant or idk? I was underimpression I should register once in a central place and then projects should plug themselves into it via

named("checkDebug")

Projects cannot plug in in any clean way

I see, somultiple registers of the same name is idiomatic & performant

Yes, they should not really be a performance issue I'd say. But never trust anything you didn't measure yourself. :-D

So whats the upside of the other option

Of the one with the variant?

do you even need anything custom? AGP behavior changes have made it such that only the default variant (usually

debug

) is linted/tested

hmmmm

by default, yes

okay im seeing it now and its nice, I wasnt aware however im noticing it runs just

detekt

which is the weaker one so either I

check detektMain

or create my own alternative lifecycle check (and wire everything) ?

btw Im noticing one more thing that plugs into check, sqldelight verify migrations

:foo:impl:verifyDebugAppDatabaseMigration SKIPPED
:foo:impl:verifyReleaseAppDatabaseMigration SKIPPED

so I guess its probably not the way to go? or cna I somehow disable the release one?

those third-party plugins should probably adapt to match the same variants that AGP is testing. e.g. it doesn't make sense to measure code coverage of variants that weren't tested

yea, it would be super cool if I could just

./gradlew check

on CI and call it a day in a android build

fix the third parties

😄 oh boy

??? I don't use it but it definitely plugs into AGP when it can

okay I dont know much on this, I just know as a user ,than I can use sqldelight in a plain java app, no android