-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Perform symbol publication using Microsoft.SymbolUploader.Build.Task #10358
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
Conversation
dougbu
commented
May 17, 2019
- aspnet/AspNetCore-Internal#2126
- add new stage template and project that publishes symbols to MSDL and SymWeb
566b0fb
to
8740add
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://dnceng.visualstudio.com/internal/_build/results?buildId=193044 is the build to watch because the new stage won't exist in PR verification.
@joeloff the official build of the same branch (modulo irrelevant whitespace in the YAML) is still failing the Sign Check step with the same errors as described in #10241. The same thing is happening in all other AspNetCore-ci-official builds, including the one for 'master' after you merged #10340 (see https://dnceng.visualstudio.com/internal/_build/results?buildId=192996&view=logs&j=f31c9f97-4411-58e7-49ac-fc73f645e6b6&t=ef92295d-dfa0-5952-f0c2-498c3b48582b&l=128 and https://dnceng.visualstudio.com/internal/_build/results?buildId=192996&view=logs&j=f31c9f97-4411-58e7-49ac-fc73f645e6b6&t=ef92295d-dfa0-5952-f0c2-498c3b48582b&l=168). Any ideas? My guess is that using |
8740add
to
3be668e
Compare
|
3be668e
to
e73f8ae
Compare
New trial official build is https://dnceng.visualstudio.com/internal/_build/results?buildId=193490 |
bb4aaad
to
b126c9e
Compare
- aspnet/AspNetCore-Internal#2126 - add new stage template and project that publishes symbols to MSDL and SymWeb - install `dotnet` version matching global.json content - restore and build the new project
- expire symbols after 10 years (or so) - switch from stages to updating our release pipeline - revert changes to ci.yml nits: - add newlines to logging of published symbols - add `$env:DOTNET_SKIP_FIRST_TIME_EXPERIENCE` to ci.yml
b126c9e
to
502c174
Compare
🆙📅 to match what's been running fine in https://dnceng.visualstudio.com/internal/_releaseProgress?_a=release-pipeline-progress&releaseId=7988 and many previous iterations of the release pipeline. (Remaining issues are limited to excluding packages that contain assemblies lacking symbols.) This branch, modulo a rebase and newlines in the symbol packages upload list, also built successfully internally: https://dnceng.visualstudio.com/internal/_build/results?buildId=197523 And, BTW I've addressed your comments @natemcmaster |
Another Helix timeout at 4 hours. Most of the tests I looked at timed out though the failures on Debian.8.Amd64.Open were due to Merging… |