CODE_PUSH_APK_BUILD_TIME is regenerated in every build for Android apps which mean that resources are recompiled even if no other resources changes or code changes were made to the app.
This means that if no code changes are made, it can add 10-20 seconds to a build (or more depending on how many resources exist). Ideally a build with no changes should not perform any work and return almost instantly.
Reproduction
./gradlew assembleDebug then ./gradlew assembleDebug you will see at the end of the second build 100 actionable tasks: 5 executed (or more).
I would expect that running assembleDebug twice in a row would yield 100 actionable tasks: 100 up-to-date.
Additional Information
cordova-plugin-code-push version: 2.0.0
iOS/Android/Windows version: Any Android
Does this reproduce on a debug build or release build? both
Does this reproduce on a simulator, or only on a physical device? both
Description
CODE_PUSH_APK_BUILD_TIME is regenerated in every build for Android apps which mean that resources are recompiled even if no other resources changes or code changes were made to the app.
This means that if no code changes are made, it can add 10-20 seconds to a build (or more depending on how many resources exist). Ideally a build with no changes should not perform any work and return almost instantly.
Reproduction
./gradlew assembleDebugthen./gradlew assembleDebugyou will see at the end of the second build100 actionable tasks: 5 executed(or more). I would expect that runningassembleDebugtwice in a row would yield100 actionable tasks: 100 up-to-date.Additional Information