IssueTracker

I was just discussing some changes to the Gradle DSL for LintOptions, and in one particular integration test, the test was doing this:

android {
    lintOptions {
        sarifOutput file("lint-results.sarif")
    }
}

The unit test then loads the file from this path:

File sarifFile = project.file("app/lint-results.sarif");

Note how the report is written into the app folder, not somewhere under build. If you instead turned on reporting via sarifReport true, it would go under build:

File sarifFile = new File(project.getSubproject("app").getBuildDir(), "reports/lint-results-debug.sarif");

Jerome mentioned that this is bad for performance ("because the build kind of invalidates itself"). He can probably expand on this, but I think this is something the build analyzer can look for. We should inspect the DSL elements which specify output paths (there are 4 related to lint), and if the files they point to are not under build, that should be a warning.