Skip to content

Update infrastructure to consume private builds from .NET #13427

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

Conversation

adityapatwardhan
Copy link
Member

@adityapatwardhan adityapatwardhan commented Aug 13, 2020

PR Summary

Update the scripts to accept internal builds from .NET.

PR Context

PR Checklist

@iSazonov
Copy link
Collaborator

Can non-MSFT peoples access the Azure repository?

@adityapatwardhan
Copy link
Member Author

@iSazonov I don't believe so. This is predominantly for streamlining releasing PowerShell on the same day as .NET.

@iSazonov
Copy link
Collaborator

I don't believe so. This is predominantly for streamlining releasing PowerShell on the same day as .NET.

Please add a comment that it is used internally only. (Otherwise I understand that I have to install private .Net builds on my local computer.)

@adityapatwardhan
Copy link
Member Author

@rjmholt Please re-review. Feedback addressed.

@adityapatwardhan adityapatwardhan added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Aug 13, 2020
@adityapatwardhan adityapatwardhan added this to the 7.1.0-preview.6 milestone Aug 13, 2020
@adityapatwardhan adityapatwardhan merged commit c20433a into PowerShell:master Aug 13, 2020
@adityapatwardhan adityapatwardhan deleted the PSDotNetPrivateBuild branch August 13, 2020 21:52
@ghost
Copy link

ghost commented Aug 17, 2020

🎉v7.1.0-preview.6 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants