Publish symbols during release #1367
Draft
Conversation
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
hallipr
requested review from
JonathanCrd,
KarishmaGhiya,
conniey,
fanyang-mono,
g2vinay,
joshfree and
wbreza
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds symbol publishing capability to the release pipeline. Symbols are debugging files (.pdb files) that help developers debug binaries in production environments. The changes integrate a new symbol publishing job into the existing release workflow.
Key Changes
- Integrates symbol publishing into the release stage after the GitHub release tag is created
- Creates a new pipeline job template that downloads signed binaries, publishes their symbols to Microsoft's symbol server, and archives the published symbols as a pipeline artifact
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| eng/pipelines/templates/jobs/release.yml | Adds template inclusion for the new publish-symbols job into the release workflow |
| eng/pipelines/templates/jobs/publish-symbols.yml | New job template that handles downloading signed binaries, publishing symbols via azure-sdk-build-tools, and archiving the results |
hallipr
force-pushed
the
users/pahallis/publish-symbols
branch
from
226b1e8 to
801ffa3
Compare
Member
Author
|
This PR needs to wait on clarification from MSRC on how to publish portable symbols for single-file executables. Currently, we end up with a folder full of pdbs and a single .exe. To convert the portable pdbs to windows pdbs for upload, each symbols file needs a dll. |
hallipr
force-pushed
the
users/pahallis/publish-symbols
branch
7 times, most recently
from
27e640a to
dafe9fa
Compare
hallipr
force-pushed
the
users/pahallis/publish-symbols
branch
from
dafe9fa to
2f1d4de
Compare
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.
What does this PR do?
Publishes symbols during release
Pre-merge Checklist
servers/Azure.Mcp.Server/CHANGELOG.mdand/orservers/Fabric.Mcp.Server/CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies)servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentationeng/scripts/Process-PackageReadMe.ps1. See Package README/servers/Azure.Mcp.Server/docs/azmcp-commands.mdand/or/docs/fabric-commands.md.\eng\scripts\Update-AzCommandsMetadata.ps1to update tool metadata in azmcp-commands.md (required for CI)ToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptsconsolidated-tools.json/servers/Azure.Mcp.Server/docs/e2eTestPrompts.mdcrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test Pipeline