Normalize app-services groupId for mozilla-central builds and fix mozconfig check for nested Gradle - #7506
Merged
Merged
Conversation
mhammond
approved these changes
Jul 29, 2026
circleci-checks
Bot
requested review from
copyrighthero
and removed request for
a team
July 29, 2026 20:06
…config check for nested Gradle
ahochheiden
force-pushed
the
normalize-groupid-nested-gradle
branch
from
July 29, 2026 20:32
88d7e4f to
68506e1
Compare
jonesetc
pushed a commit
to jonesetc/application-services
that referenced
this pull request
Aug 12, 2026
…config check for nested Gradle (mozilla#7506)
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.
This necessary for the
application-servicesmonorepo work in Firefox. Full stack on Phabricator here: https://phabricator.services.mozilla.com/D298762In
mozilla-central, a-s always publishes underorg.mozilla.appservices,never the
.nightlyvariant. The mozconfig property lives on the rootGradle instance, so the check uses
gradle.rootto work when thissettings.gradle is included from a nested build (m-c includes it from
android-components and fenix).