-
Notifications
You must be signed in to change notification settings - Fork 280
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 "vcpkg configure environment" release pipeline and subcommands. #277
Conversation
ffb510e
to
9fa245b
Compare
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 forgot to post these earlier, so my apologies if they don't line up with the current files.
4ddad43
to
15034d3
Compare
8053741
to
50b1c6d
Compare
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.
Requesting revert of the vcpkg list
breaking changes before merge
Until you just go to using a submodule, you should get the CE repo via clone/checkout so that the set-versions script works correctly.
…CPKG.EXE (#280) (or something else would be ok -- just add a double-dash style switch at the end of the whole command `--whatever`)
…election command.
…y on command lines. This test was broken by updating the vcpkg-scripts-sha to a contemporary version.
7237f07
to
f615160
Compare
6d99b64
to
c95e1dc
Compare
This adds the "vcpkg configure environment" formerly-separate-product commands to vcpkg. "vcpkg-ce", formerly "Project Cella" formerly "Project Northfield" is an incubating separate product to get vcpkg solving for all build time dependencies, including tooling, rather than only sources. Initial releases touching these commands will be in a very rough "collect feedback" state, and the commands may be changed or removed at any time. (Completely separating from the vcpkg command proper is still a possible outcome, for example)
This change incorporates many peoples' work, not only my own, and will not be squashed. In particular, but not limited to:
The new release process if there are updates to the "configure environment" components is:
git fetch origin && git push internal origin/main:main
, which kicks off producing the signed builds as described here inazure-pipelines/signing.yml
. This ensures that things signed by Microsoft are actually from Microsoft.