-
Notifications
You must be signed in to change notification settings - Fork 331
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
Automatic post-build symbol availability validation #173
Comments
Tracked in #167 |
That's not the case--I described the relationship between these two issues in the description of the other issue:
I'm reopening this--they're very distinct scenarios. The release team is what needs this tooling to include as a release step to make sure both the symbol publish tooling works and the symbol server accepted the symbols. It's the build infra's responsibility to provide the correct symbols to the release infrastructure, which is why I see this dividing line as very important. /cc @leecow |
Closing this since now we have a short term solution (#2534) and another issue for a long term solution (dotnet/arcade-services#2465) |
@dagood commented on Tue May 15 2018
Validate that the symbols made it to the official public symbol server endpoint after each build.
per @mikem8361 : build a tool using the Microsoft.SymbolStore support from the symstore repo/feed https://github.com/dotnet/symstore that index and verify PDB and DLLs are on any symbol server.
The text was updated successfully, but these errors were encountered: