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

Place smoke test build output in the tarball's artifacts directory #2793

Closed
MichaelSimons opened this issue Mar 9, 2022 · 1 comment
Closed

Place smoke test build output in the tarball's artifacts directory #2793

MichaelSimons opened this issue Mar 9, 2022 · 1 comment
Labels
area-testing Improvements in CI and testing

Comments

@MichaelSimons
Copy link
Member

The value of doing this is all artifacts are placed in a single location which makes cleanup easier. Another goal is to eliminate net6.0 from the artifacts path which gets referenced in the build pipeline. This eliminates chances of breaking the build over time.
@MichaelSimons MichaelSimons moved this to 6.0 On Deck in .NET Source Build Mar 9, 2022
@dotnet-issue-labeler dotnet-issue-labeler bot added area-testing Improvements in CI and testing untriaged labels Mar 9, 2022
@MichaelSimons MichaelSimons moved this from 6.0 On Deck to 7.0 Backlog in .NET Source Build Mar 10, 2022
@MichaelSimons MichaelSimons moved this from 7.0 Backlog to 8.0 Backlog in .NET Source Build Sep 7, 2022
@MichaelSimons MichaelSimons mentioned this issue Nov 14, 2022
Closed
@MichaelSimons MichaelSimons moved this from Needs Review to Backlog in .NET Source Build Jun 8, 2023
@MichaelSimons
Copy link
Member Author

This was completed with dotnet/installer#19290

@github-project-automation github-project-automation bot moved this from Backlog to Done in .NET Source Build Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-testing Improvements in CI and testing
Projects
.NET Source Build
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MichaelSimons