-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Restructure the package build to simplify signing and packaging stages #19321
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
Restructure the package build to simplify signing and packaging stages #19321
Conversation
<
10000
a title="Only build assemblies" data-pjax="true" class="Link--secondary markdown-title" href="/PowerShell/PowerShell/pull/19321/commits/4e5c3e212935f9db583cf435acaee67af35db196">Only build assemblies
|
||
strategy: | ||
matrix: | ||
linux-x64: |
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 should consider dynamically producing the matrix, so we can move it into a single JSON in our repo as we need this matrix in more places.
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 can do that as part of the next iteration, i need to split the deb build and packaging.
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
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.
LGTM
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
PR Summary
Re-structure the release build to simplify the packaging and signing stages. More changes will be made to simplify linux build and packaging in future PRs.
PR Context
PR Checklist
.h
,.cpp
,.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
or[ WIP ]
to the beginning of the title (theWIP
bot will keep its status check atPending
while the prefix is present) and remove the prefix when the PR is ready.(which runs in a different PS Host).