Build: publish libraries directly to NewAndroid feed, Fixes AB#3609347#2512
Open
fadidurah wants to merge 3 commits into
Open
Build: publish libraries directly to NewAndroid feed, Fixes AB#3609347#2512fadidurah wants to merge 3 commits into
fadidurah wants to merge 3 commits into
Conversation
Switches Maven publishing from the AndroidADAL feed to the NewAndroid feed to eliminate the upstream-feed traversal latency that occurs when downstream pipeline stages resolve freshly-published artifacts. Background: - Builds publish to AndroidADAL but consumers fetch from NewAndroid. - NewAndroid resolves AndroidADAL only via its upstream chain, after walking Maven Central, Google, etc., causing first-fetch latency on every newly published version (which CI agents always pay due to ephemeral caches). - AndroidADAL will be added as an upstream of NewAndroid (done outside this change) so any external consumers still resolving from AndroidADAL keep working transparently. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
Contributor
There was a problem hiding this comment.
Pull request overview
Switches the Maven publish target URL in msal/build.gradle from the AndroidADAL feed to the NewAndroid feed to avoid upstream-feed traversal latency on CI dependency resolution.
Changes:
- Update the publishing repository URL to point at the
NewAndroidAzure DevOps feed.
When configure-on-demand is enabled, Gradle only configures the projects that are actually in the dependency graph of the requested tasks. Previously building AADAuthenticator triggered configure of broker4j, brokerHost, java-linux-test-app, LinuxBroker, brokerautomationapp etc. — none of which are needed for AADAuthenticator:assembleDistRelease. Logs showed ~16 min spent in unnecessary configure phases. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
darasok85az-lang
approved these changes
May 15, 2026
|
✅ Work item link check complete. Description contains link AB#3609347 to an Azure Boards work item. |
github-actions
Bot
changed the title
p3dr0rv
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AB#3609347
Summary
Switches Maven publishing from the
AndroidADALfeed to theNewAndroidfeed to eliminate upstream-feed traversal latency on dependency resolution in CI.Why
NewAndroidonly hasAndroidADALconfigured as an upstream, after Maven Central / Google / etc. Every newly-published version pays a full upstream walk on first resolve.Companion changes
AndroidADALwill 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.microsoft-authentication-library-common-for-android,microsoft-authentication-library-for-android,ad-accounts-for-android, and theAuthClientAndroidPipelines1ES repo make the same flip.Risk
Low — same Azure DevOps organization, same auth, same package coordinates, same retention. Only the publish-target feed name changes.