Improve build performance

[ecgreb]

Overview

Improves build performance on Circle CI. Reduces build time by 1-2 min for dev builds and 4-5 min for full master builds (includes sample apps). Prevents OOM errors on Circle CI container.

Proposed Changes

• Updates Gradle options to limit memory use and dump heap on OOM error.
• Runs unit tests against debug build only and reduces console output.
• Upgrades Gradle to version 3.3 and gradle-android-maven-plugin to version 1.5.
• Adds --configure-on-demand and -PdisablePreDex options to circle.yml.
• Runs tests for each module in parallel using 3 Circle CI containers instead of 1.
• Archives sample app APKs on Circle CI and deploys to AWS on release build only.
• Publishes documentation to Mapzen website on release build only.
• Installs core module to local .m2 repo before resolving dependencies.
• Disables Javadoc tasks for all modules. May need to be re-enabled for production AARs.

Fixes #297

[tallytalwar]

Starting reviewing this now.

[tallytalwar]

Looks good to go. 👍 Happy master builds now!

[tallytalwar]

👍 Nicely documented in gradle docs (which sometimes are very convoluted, at least for me): https://docs.gradle.org/current/userguide/multi_project_builds.html#sec:configuration_on_demand

[tallytalwar]

The only information I found for this is its recommended to use -PdisablePreDex when doing a one time build (typical with CI env.). But no finer details behind the reasoning. Can you point me to a reference/explain? Thanks

[ecgreb]

Using -PdisablePreDex was recommended in this Circle CI issue.

[tallytalwar]

naive question ... when does PERFORM_RELEASE get set?

[ecgreb]

Haha it does not yet! :) I will be adding a script to perform the release using Circle's API similar to this one we use for Eraser Map as part of #279.