Skip to content

Implement VMR PR pipeline #3823

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
Closed
Tracked by #4074
mmitche opened this issue Jan 3, 2024 · 5 comments
Closed
Tracked by #4074

Implement VMR PR pipeline #3823

mmitche opened this issue Jan 3, 2024 · 5 comments
Assignees
@akoeplinger
Labels
area-unified-build

Comments

@mmitche
Copy link
Member

mmitche commented Jan 3, 2024 •
edited
Loading

We have a PR pipeline today based out of the installer repo. This will need to move to the VMR repo.

T-Shirt Size: Small
@mmitche mmitche converted this from a draft issue Jan 3, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added area-build Improvements in source-build's own build process untriaged labels Jan 3, 2024
@ViktorHofer
Copy link
Member

It looks like we already have a PR pipeline in dotnet/dotnet: dotnet/dotnet#46

@MichaelSimons MichaelSimons added area-unified-build and removed area-build Improvements in source-build's own build process untriaged labels Jan 4, 2024
@mmitche
Copy link
Member Author

mmitche commented Jan 4, 2024

It's not the final pipeline, likely. That will require some more thought probably.

@mmitche mmitche mentioned this issue Jan 5, 2024
Closed
66 tasks
@tkapin tkapin mentioned this issue Jan 11, 2024
Open
@ViktorHofer
Copy link
Member

Requirements:

  1. Add a few initial legs for building without building from source on Windows, Ubuntu and macOS
  2. Add those legs to the installer PR
  3. Also run them as official builds so that we can compare the produced assets with the current Windows official build
  4. Disable repos that currently don't build when not building from source via an exclusion mechanism.

@mmitche mmitche moved this to Ready in .NET Unified Build Jan 24, 2024
@mmitche
Copy link
Member Author

mmitche commented Jan 24, 2024

Marking as Ready

This was referenced Jan 24, 2024
Closed
Merged
Merged
@akoeplinger akoeplinger mentioned this issue Jan 26, 2024
Merged
@mmitche mmitche moved this from Ready to In Progress in .NET Unified Build Jan 30, 2024
@mmitche mmitche mentioned this issue Jan 31, 2024
Closed
3 tasks
akoeplinger added a commit to dotnet/installer that referenced this issue Feb 6, 2024
@akoeplinger
Add VMR unified build pipelines (#18409)
28012e7 
Contributes to dotnet/source-build#3823

- Removes and consolidates vmr-cross-build.yml/ci-cross-build.yml POC into vmr-build.yml/ci.yml
- Add stage for building vertical/unified build legs into vmr-build.yml
- Adds Windows build and handling for Windows/Unix differences
@akoeplinger
Copy link
Member

This was done.

@github-project-automation github-project-automation bot moved this from In Progress to Done in .NET Unified Build Feb 7, 2024
v-wuzhai pushed a commit to dotnet/sdk that referenced this issue Apr 22, 2024
@akoeplinger
Add VMR unified build pipelines (#18409)
667988b 
Contributes to dotnet/source-build#3823

- Removes and consolidates vmr-cross-build.yml/ci-cross-build.yml POC into vmr-build.yml/ci.yml
- Add stage for building vertical/unified build legs into vmr-build.yml
- Adds Windows build and handling for Windows/Unix differences
ViktorHofer pushed a commit to dotnet/sdk that referenced this issue May 7, 2024
@akoeplinger
Add VMR unified build pipelines (#18409)
5530b80 
Contributes to dotnet/source-build#3823

- Removes and consolidates vmr-cross-build.yml/ci-cross-build.yml POC into vmr-build.yml/ci.yml
- Add stage for building vertical/unified build legs into vmr-build.yml
- Adds Windows build and handling for Windows/Unix differences
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akoeplinger akoeplinger

Labels
area-unified-build
Projects
.NET Unified Build
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@akoeplinger @ViktorHofer @MichaelSimons @mmitche