-
Notifications
You must be signed in to change notification settings - Fork 358
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
Add support for dotnetbuilds-published dotnet cli packages #8162
Conversation
$installParameters.FeedCredential = $decodedString | ||
} | ||
$dotnetBuilds = $installParameters.Clone() | ||
$dotnetbuilds.AzureFeed = "https://dotnetbuilds.azureedge.net/public" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't think we had a CDN for this account, is this right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fancy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple questions, but looks generally okay.
Write-PipelineTelemetryError -Category 'InitializeToolset' -Message "Failed to install dotnet from custom location '$runtimeSourceFeed'." | ||
ExitWithExitCode 1 | ||
} | ||
if ($runtimeSourceFeed) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we going to need a variation for dotnetbuilds/internal? Or would we be planning on replacing the existing usage of runtimesourcefeed as dotnetclimsrc in the repos with dotnetbuilds/internal instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, we should just use dotnetbuilds/internal in place of dotnetclimsrc in our current workflow
This change adds support for installing dotnet cli packages that were published to dotnetbuilds to both the helix sdk FindDotNetCliPackage task, and the build scripts.