Optimize incremental builds for android/gradle

We have lot of 'grandfathered' issues which we are fixing, below are the workflow we typically use

```

1. ./gradlew clean
2. infer --reactive -- ./gradlew --offline assembleDebug
3. Note down the issues and fix
4. infer --reactive --continue -- ./gradlew --offline assembleDebug

```

Above works fine, however step 4 seems to analyse the complete project even though only 1 file changed and it takes more time to analyse and report.

is there any flags or options which we can use to build only a file or two when using gradle, I'm aware its possible for normal java builds but how about gradle builds?