Skip to content

Commit a4ad7f0

Browse files
fadidurahCopilot
andauthored
Build perf: enable Gradle configure-on-demand, Fixes AB#3609347 (#2512)
[AB#3609347](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3609347) ## Summary Switches Maven publishing from the `AndroidADAL` feed to the `NewAndroid` feed to eliminate upstream-feed traversal latency on dependency resolution in CI. ## Why - We publish artifacts to **AndroidADAL** but consumers (including downstream pipeline stages in the same release) fetch from **NewAndroid**. - `NewAndroid` only has `AndroidADAL` configured as an upstream, **after** Maven Central / Google / etc. Every newly-published version pays a full upstream walk on first resolve. - CI agents are ephemeral (no Gradle cache reuse), so pipelines pay this penalty on every run for every fresh dependency. - Publishing **directly to NewAndroid** removes the upstream walk and speeds up chained library/test-app builds. ## Companion changes - `AndroidADAL` will be added as an **upstream of NewAndroid** (manual step in ADO Artifacts UI, outside this PR) so any external consumers still resolving from AndroidADAL keep working. - Sister PRs in `microsoft-authentication-library-common-for-android`, `microsoft-authentication-library-for-android`, `ad-accounts-for-android`, and the `AuthClientAndroidPipelines` 1ES repo make the same flip. - ADAL is intentionally excluded (legacy library). - Authenticator is intentionally excluded. ## Risk Low — same Azure DevOps organization, same auth, same package coordinates, same retention. Only the publish-target feed name changes. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 2596e2d commit a4ad7f0

2 files changed

Lines changed: 2 additions & 1 deletion

File tree

common

Submodule common updated 82 files

gradle.properties

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ android.enableJetifier=true
77
# https://office.visualstudio.com/Outlook%20Mobile/_wiki/wikis/Outlook-Mobile.wiki/3780/Android-Studio-Gradle-Performance-tips-and-tricks
88
org.gradle.parallel=true
99
org.gradle.daemon=true
10+
org.gradle.configureondemand=true
1011

1112
# See https://stackoverflow.com/questions/56075455/expiring-daemon-because-jvm-heap-space-is-exhausted
1213
# we must make sure that the total size is <7G, as that's the RAM size of VM on the build pipeline.

0 commit comments

Comments
 (0)