Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tell PublishSymbols task about binaries as well as the PDB files #11852

Merged
5 commits merged into from
Dec 2, 2021

Conversation

miniksa
Copy link
Member

@miniksa miniksa commented Dec 1, 2021

We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks.

PR Checklist

… feed binaries into the indexer engine as well for improved symbol reliability while debugging, especially around thrown exceptions.
@ghost ghost added Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Task It's a feature request, but it doesn't really need a major design. Product-Meta The product is the management of the products. labels Dec 1, 2021
@miniksa
Copy link
Member Author

miniksa commented Dec 1, 2021

Oof. Problem. Have to exclude the packages folder for binaries... Or restrict the search paths to the bin directories or artifacts directories instead of matching everything...

@zadjii-msft zadjii-msft added the AutoMerge Marked for automatic merge by the bot when requirements are met label Dec 1, 2021
@ghost
Copy link

ghost commented Dec 1, 2021

Hello @zadjii-msft!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@zadjii-msft zadjii-msft removed the AutoMerge Marked for automatic merge by the bot when requirements are met label Dec 1, 2021
@miniksa
Copy link
Member Author

miniksa commented Dec 1, 2021

hold please still fixing stuff

@github-actions

This comment has been minimized.

@ghost ghost added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Dec 1, 2021
Copy link
Member

@DHowett DHowett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is crazy to me, but I am totally fine with installing the Windows SDK as part of the build. Wow, though. Just, wow.

@miniksa miniksa added the AutoMerge Marked for automatic merge by the bot when requirements are met label Dec 2, 2021
@ghost ghost merged commit 52235b0 into main Dec 2, 2021
@ghost ghost deleted the dev/miniksa/symbols branch December 2, 2021 00:02
DHowett pushed a commit that referenced this pull request Dec 13, 2021
)

We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks.

## PR Checklist
* [x] Closes #11737 - main fix for feeding EXEs and DLLs into the symbol publisher
* [x] Closes #11860 - bonus fix because I noticed the PDB source linking wasn't working
* [x] I work here.
* [x] If it fits, it sits.

(cherry picked from commit 52235b0)
DHowett pushed a commit that referenced this pull request Dec 13, 2021
)

We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks.

## PR Checklist
* [x] Closes #11737 - main fix for feeding EXEs and DLLs into the symbol publisher
* [x] Closes #11860 - bonus fix because I noticed the PDB source linking wasn't working
* [x] I work here.
* [x] If it fits, it sits.

(cherry picked from commit 52235b0)
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta AutoMerge Marked for automatic merge by the bot when requirements are met Issue-Bug It either shouldn't be doing this or needs an investigation. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Meta The product is the management of the products.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PDB source linking step isn't working Validate symbol indexing status per PkgES guidance
4 participants