We have a lot offake/demo/testing style projects that are only intended for consumption by debug variant apps. Some of these have onlydebug/ sourcesets. In a perfect world, we would use single-variant android libraries and rely on other tooling to ensure these projects never end up in release builds. Our current state leaves us with a lot of complications if we try to run analysis on both debug and release variants because these debug-only projects often fail to compile in the release configuration, or we are just wasting time by analyzingreleaseUnitTest stuff.

I'd propose this as an intermediate solution until a v3.0 where we might have a more advanced DSL for exclusions. What I'd really like to do is be able to exclude release variants for test source sets everywhere.

feat: Add variant exclusion per-project in DSL

8fe3aa5

autonomousapps reviewed

May 29, 2025

View reviewed changes

Copy link

Owner

autonomousapps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Why is this on the AbiHandler? The way it's used, it looks like it's causing the variant to be ignored for all use-cases, not just ABI analysis. And given that, why isn't the existing functionality toignore specific source sets sufficient?

Copy link

ContributorAuthor

joshfriend commentedMay 29, 2025

Why is this on the AbiHandler?

I got it mixed up with theProjectIssueHandler handler, what I was going for was a project specific version of the global propertydependency.analysis.android.ignored.variants that exists currently.

why isn't the existing functionality toignore specific source sets sufficient?

If I have an Android project with only adebug/ source set, and I useignoreSourceSet('release') DAGP still compiles and analyzes the variant (or it tries to and fails because the release configuration of some of these debug-only projects is often broken).