Ensure symbols are always published during VS insertion - #2555
Open
Sabrina Faceroli Tridico (safacero) wants to merge 1 commit into
Open
Ensure symbols are always published during VS insertion#2555Sabrina Faceroli Tridico (safacero) wants to merge 1 commit into
Sabrina Faceroli Tridico (safacero) wants to merge 1 commit into
Conversation
Sabrina Faceroli Tridico (safacero)
changed the title
Skip optional commit/work-item enrichment on the insertion step, and make the symbol download and archive steps always run so debug symbols are published even if a later step reports a non-fatal error. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sabrina Faceroli Tridico (safacero)
force-pushed
the
safacero/fix-symbolcheck-insertion-symbols
branch
from
July 6, 2026 20:30
fbd4e2f to
2e1c35a
Compare
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
1 participant
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.
Makes the VS insertion pipeline more robust so that debug symbols are always published, even if a later step in the insertion job reports a non-fatal error.