-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
CI - Sign and symbol upload Cross OS DAC #33528
Comments
Per @mikem8361
Per @leculver & @mikem8361 suggestions the new DAC should be indexed as:
|
Per @dagood I believe @jashook is the right person to talk about implementation. The artifact I think you need to end up with is a symbol package that contains the cross OS DAC + target platform libcoreclr, so the files are adjacent and hit the symbol uploader tool’s convention to pick up the desired build id. If those native bits can’t be built on the same platform as the libcoreclr, the way to get them together is a “join job” that depends on multiple earlier jobs to finish then downloads the artifacts to repackage. Currently every Installer job joins all CoreCLR and Libraries jobs, because Installer has to read some data from every artifact on every platform to make the full platform manifest. (But we want to stop this: Create full platform manifest in local build (don't require job join) #1622.) That can maybe be used as an example to create a new job that makes cross OS DAC indexing symbol packages. |
not me! probably meant to ping some other @ |
Sorry about that! It was pasted from an email (where that resolves to the right person). Edited. |
This was completed in #39574 |
We need to revise the official build process to
We need to agree on the indexing scheme and update the symbol upload docs.
We will need add indices to support mapping from the following libcoreclr build-ids to the corresponding Windows DAC.
The text was updated successfully, but these errors were encountered: