Fix MicroBuild JAR signing regression - #12293
Merged
Miller Wang (wangmingliang-ms) merged 1 commit intoAug 17, 2026
Merged
Conversation
Pin the last known-good signing package, forward the build access token, and fail immediately when DDSignFiles returns an error. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
Miller Wang (wangmingliang-ms)
deleted the
wangmi/fix-microbuild-signing
branch
August 17, 2026 01:45
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
2 participants
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.
Summary
MicroBuild.Plugins.Signingto the last known-good1.1.1330releaseSystem.AccessTokento plugin installation and JAR signingDDSignFilesreturns a non-zero exit codeRoot cause
Scheduled real-sign builds started failing after the signing package automatically moved from
1.1.1330to1.1.1374. The newer package looks for authentication certificateea4022a2-6f71-4214-88b6-18d2bbd6b4cc, while PME installsAUTH-CORPwith subjectdec434ad-6bd4-4a20-b400-4bf6db7fc3fb.The signing loop also ignored the failed process exit code, causing the task to retry every JAR until its four-hour timeout.
Failed build: https://mseng.visualstudio.com/VSJava/_build/results?buildId=31892392
Validation
git diff --check