facebook/infer

Optimize incremental builds for android/gradle

Open

#532 opened on Dec 8, 2016

View on GitHub
 (2 comments) (0 reactions) (0 assignees)HTML (12,410 stars) (1,688 forks)batch import
enhancementhelp wantedintegration

Description

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?

Contributor guide

Tech stack
javaandroid
Domain
build systemperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Knowledge of Infer static analyzerExperience with Gradle build systemAndroid development basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how Infer handles incremental builds with Gradle. Review the Infer Gradle plugin configuration and the reactive analysis mode. Check if there are existing flags in Gradle to only analyse changed files. Refer to the Infer source code for build system integration, e.g., in the 'infer' repository under 'src/gradle' or similar.