Skip to content
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

SourceBuild leg is not using source-built arcade #66514

Closed
ericstj opened this issue Mar 11, 2022 · 3 comments
Closed

SourceBuild leg is not using source-built arcade #66514

ericstj opened this issue Mar 11, 2022 · 3 comments

Comments

@ericstj
Copy link
Member

ericstj commented Mar 11, 2022

We discovered in #66144 that our source-build validation leg doesn't use any of the source-built arcade packages.

@akoeplinger discovered this previously here: dotnet/arcade#8355

This can be observed in the binlog by examining the task assemblies used. Many of the packages/SDKs (including arcade SDK itself) are using non-source built packages.

Source-build is tracking fixing the route problem in dotnet/arcade#8642

This issue will track removing workarounds from dotnet/runtime.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 11, 2022
@ghost
Copy link

ghost commented Mar 11, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

We discovered in #66144 that our source-build validation leg doesn't use any of the source-built arcade packages.

@akoeplinger discovered this previously here: dotnet/arcade#8355

This can be observed in the binlog by examining the task assemblies used. Many of the packages/SDKs (including arcade SDK itself) are using non-source built packages.

Source-build is tracking fixing the route problem in dotnet/arcade#8642

This issue will track removing workarounds from dotnet/runtime.

Author: ericstj
Assignees: -
Labels:

area-Infrastructure, untriaged

Milestone: -

@ericstj
Copy link
Member Author

ericstj commented Mar 11, 2022

Closing this as we chose not to workaorund it in dotnet/runtime and instead are working around in arcade. dotnet/arcade#8597

@ericstj ericstj closed this as completed Mar 11, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Apr 16, 2022
@jeffhandley jeffhandley removed the untriaged New issue has not been triaged by the area owner label May 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants