Optimize incremental builds for android/gradle · facebook/infer#532

(2 留言) (0 反應) (0 負責人)HTML (12,410 star) (1,688 fork)batch import

enhancementhelp wantedintegration

描述

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?

貢獻者指南

技術棧: javaandroid
領域: build systemperformance
議題類型: performance
難度: 3
預計時間: half day
活動狀態: stale
清晰度: clear
前置要求: Knowledge of Infer static analyzerExperience with Gradle build systemAndroid development basics
新手友善度: 30
研究方向: 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.