Skip to content

Enable consuming public .NET SDK builds from the VMR using DarcLib #6379

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

Merged
merged 8 commits into from
Apr 21, 2025

Conversation

lbussell
Copy link
Contributor

This PR is a draft since it's based on #6378. It will be rebased once that PR is merged.

Adds a new command from-channel which takes a channel and repo to get the latest build from. It should only work for the VMR for now. In the future maybe we'll allow other repos like monitor, yarp, aspire, etc..

This iteration of the code simply gets the new .NET versions from BAR by reading a single build asset containing those versions. Then it sets up a call to the specific versions command and executes it. So, we are still relying on SpecificCommand and all its code for resolving product version hashes. In the future, all versions and hashes should be read directly from the BAR build. But this is the MVP for consuming VMR builds.

Todo:

  • Authentication for automated version updates

@lbussell lbussell marked this pull request as ready for review April 18, 2025 18:12
@lbussell lbussell requested a review from a team as a code owner April 18, 2025 18:12
@lbussell lbussell changed the title Enable consuming public .NET SDK builds from the VMR Enable consuming public .NET SDK builds from the VMR using DarcLib Apr 18, 2025
Asset {asset.Name} has {asset.Locations.Count} locations:
{allLocations}
""",
asset.Name, asset.Locations.Count, allLocations);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These extra arguments are unnecessary since you already referenced them in the string interpolation. This applies to some other usages throughout this PR too.

Copy link
Contributor Author

@lbussell lbussell Apr 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a quirk of Microsoft.Extensions.Logging. It does its own string interpolation, and you get an IDE warning if you use the built-in string interpolation. This is so that the logger implementation can capture the actual values of the things you pass in for filtering and analysis later. And reduces the runtime overhead of performing the string interpolation if logging is turned off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants