Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
| 1. - [ ] Run poison report and confirm results. | ||
| 1. - [ ] Compare source-built to Microsoft build and confirm results. | ||
| 1. - [ ] [Internal] Gather smoke-test prereqs and package in dotnet-smoke-test-prereqs-6.0.101.tar.gz. | ||
| 1. - [ ] [Internal] Upload source and smoke-test-prereqs tarball to dotnetclimsrc storage account. |
There was a problem hiding this comment.
If it's not an internal build, how do partners acquire a tarball? In 5.0, if it was not an internal build, we gave them a commit in source-build that they then needed to pull, build a production build and then create a tarball from that. In 6.0, we should be able to give them a commit in installer and they need to 1) find the commit, 2) go to the (hopefully successful) build for that commit, 3) download the BlobArtifacts zip file for that build and 4) extract the tarball from the zip. Or, we could just send a link to the URL for the BlobArtifacts. Either way, this should maybe be included in the checklist.
There was a problem hiding this comment.
Good point. I added a [Non-Internal] item to cover this.
No description provided.