Uh oh!
There was an error while loading. Please reload this page.
[Infra] Revert removal of clr dependency from mono builds - #62788
Conversation
ghost
commented
Dec 14, 2021
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis partially reverts this change: #62652 The problem is that although we no longer need to patch, we do need corerun from the clr.hosts subset. Corerun still ends up as part of the pubished clr product artifact, and not in the mono product artifact. And thus we still end up downloading clr, and still need this dependency for now.
|
safern
commented
Dec 14, 2021
Why not publish it as part of the mono artifacts? Is it because of the artifacts layout structure? I guess it doesn't make sense to invest on that since we are going to collapse the jobs? |
naricc
commented
Dec 14, 2021
@safern I was going to try to publish it as part of mono's artifacts, but I looked at the yml files and didn't immediately understand how to do that. So I was going to do this revert while I figure it out. Any pointers on what needs to change? Is it easy? |
lambdageek
commented
Dec 14, 2021
Yea, the ArchiveFiles azdo task seems to want a single root folder. So we'd have to arrange for |
This partially reverts this change: #62652
The problem is that although we no longer need to patch, we do need corerun from the clr.hosts subset. Corerun still ends up as part of the pubished clr product artifact, and not in the mono product artifact. And thus we still end up downloading clr, and still need this dependency for now.