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.

Sign up for GitHub

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

Jump to bottom

Clean up AnyOS handling in build-test-job.yml #61790

Open
jkoritzinsky opened this issue Nov 18, 2021 · 1 comment
Open

Clean up AnyOS handling in build-test-job.yml #61790

jkoritzinsky opened this issue Nov 18, 2021 · 1 comment
Labels
area-Infrastructure help wanted [up-for-grabs] Good issue for external contributors
Milestone
Future

Comments

@jkoritzinsky
Copy link
Member

As part of the runtime test build reorganization, we introduced some special cases in build-test-job.yml where instead of using $(managedTestArtifactRootFolderPath) for the upload path, we manually build the folder name. We should investigate refactoring how we set managedTestArtifactRootFolderPath so we can go back to using it in all cases.
@jkoritzinsky jkoritzinsky added help wanted [up-for-grabs] Good issue for external contributors area-Infrastructure untriaged New issue has not been triaged by the area owner labels Nov 18, 2021
@ghost
Copy link

ghost commented Nov 18, 2021

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

Issue Details

As part of the runtime test build reorganization, we introduced some special cases in build-test-job.yml where instead of using $(managedTestArtifactRootFolderPath) for the upload path, we manually build the folder name. We should investigate refactoring how we set managedTestArtifactRootFolderPath so we can go back to using it in all cases.

Author: jkoritzinsky
Assignees: -
Labels:

up-for-grabs, area-Infrastructure, untriaged
Milestone: -

This was referenced Nov 18, 2021
Merged
Merged
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Nov 20, 2021
@agocke agocke added this to the Future milestone Jul 11, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-Infrastructure help wanted [up-for-grabs] Good issue for external contributors
Projects
Runtime Infra
Status: No status
Milestone
Future
Development

No branches or pull requests
2 participants
@agocke @jkoritzinsky