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

logic to capture runtime-portable artifacts/logs does not handle rebuilds well #2936

Closed
MichaelSimons opened this issue Jul 6, 2022 · 1 comment
Labels
area-infra Source-build infrastructure and reporting

Comments

@MichaelSimons
Copy link
Member

There is special logic in the runtime-portable tarball project to handle copying the portable artifacts in prep for the non-portable runtime build. This logic resides in the CleanupRepoForNonPortableBuild target. This logic does not handle rebuilds well upon successfully building the runtime-portable repo. The logic ends up creating nested portableLog and portableObj directories. When this occurs it is difficult to find the original artifacts.

@dotnet-issue-labeler dotnet-issue-labeler bot added area-infra Source-build infrastructure and reporting untriaged labels Jul 6, 2022
@MichaelSimons
Copy link
Member Author

This issue is obsolete. The runtime-portable build was removed with #3027.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infra Source-build infrastructure and reporting
Projects
Archived in project
Development

No branches or pull requests

1 participant