Repository navigation
[build] Serialize Gradle wrapper projects - #12424
Merged
Merged
Conversation
Prevent concurrent single-use Gradle daemons from racing on the shared daemon registry during parallel solution builds. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b034b140-f3bb-448c-8e47-ec4fd8d6100d
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the internal build graph to prevent parallel builds from running multiple Gradle-wrapper-based projects at the same time, reducing Gradle daemon startup contention (e.g., “Timeout waiting to connect to the Gradle daemon”) during solution builds.
Changes:
- Add an ordering-only
ProjectReferencefromproguard-androidtor8to serialize Gradle wrapper project execution. - Document the intent inline in
proguard-android.csprojwith a short comment.
Member
Author
|
@dalexsoto review |
jonathanpeppers
added
the
ready-to-review
dalexsoto
approved these changes
Aug 18, 2026
dalexsoto
left a comment
dalexsoto
left a comment
Member
There was a problem hiding this comment.
The ordering-only project reference safely serializes Gradle wrapper builds without introducing graph cycles or output dependencies.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pull Request
title and
description
should follow the
commit-messages.mdworkflow documentation, and in particular should include:Useful description of why the change is necessary.
Parallel solution builds can launch
proguard-androidalongside other projects using the shared Gradle wrapper. Gradle 9.4.1 can then fail while starting a single-use daemon withTimeout waiting to connect to the Gradle daemonas the processes contend on the shared daemon registry.Add an ordering-only reference from
proguard-androidtor8. Sincer8already waits onmanifestmerger, this places all wrapper projects in one serialized chain while preserving the directandroidsdkdependency.Links to issues fixed
N/A
Unit tests
N/A - this changes only MSBuild project ordering. The
proguard-androidproject chain builds successfully.