-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[vcpkg] Add vcpkg export
to E2E tests. Enable E2E tests on all platforms.
#12198
[vcpkg] Add vcpkg export
to E2E tests. Enable E2E tests on all platforms.
#12198
Conversation
bb22dcb
to
17a7551
Compare
5c9c867
to
19ddebe
Compare
19ddebe
to
ab03cdc
Compare
Don't forget to remove new vcpkg_downloads references when resolving the merge |
# Conflicts: # scripts/azure-pipelines/windows/azure-pipelines.yml
@ras0219 @ras0219-msft @strega-nil e2e99d0 contains 'interesting' merge conflict resolutions from #12314 |
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'm curious about the one thing; also, do variables
automagically get turned into environment variables?
|
…forms. (microsoft#12198) * [vcpkg] Add `vcpkg export` to E2E tests. Enable E2E tests on MacOS. * [vcpkg] Fix export --raw --output-dir=/path/ by changing directory to new export root Co-authored-by: Robert Schumacher <[email protected]> Co-authored-by: Billy Robert O'Neal III <[email protected]>
See title.
In order to enable compartmentalized testing, also adds
vcpkg export --output-dir=/export/artifacts/
. This is implemented for all first-party export mechanisms, however I have declined to implement it for experimental community export mechanisms because we do not have reliable testing for them.