Skip to content
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

appveyor: publish artifacts on appveyor #4509

Closed
wants to merge 1 commit into from

Conversation

janisozaur
Copy link
Contributor

This allows obtaining upstream builds of curl directly from appveyor for
all the available configurations

This allows obtaining upstream builds of curl directly from appveyor for
all the available configurations
@bagder
Copy link
Member

bagder commented Oct 21, 2019

So where/how do you find the artifacts after a build?

@jay
Copy link
Member

jay commented Oct 24, 2019

There is an undocumented curl tool switch for Windows to get all the module paths --dump-module-paths so to figure out which OpenSSL dependencies to make artifacts you could do curl --dump-module-paths | grep -iv "^C:\\Windows\\\\"

@jay jay added the Windows Windows-specific label Oct 24, 2019
@janisozaur
Copy link
Contributor Author

@bagder sorry for late response, I didn't notice your comment.

You have to select a particular build job from the matrix, e.g. https://ci.appveyor.com/project/curlorg/curl/builds/28233363/job/haokjn1m953utws3

then switch to 'artifacts' tab

image

There's more documentation available here: https://www.appveyor.com/docs/packaging-artifacts/#permalink-to-the-last-successful-build-artifact

In particular you can offer CI builds using the permalink constructed as described in the link.

@bagder
Copy link
Member

bagder commented Oct 30, 2019

Thanks!

@bagder bagder closed this in 8d8b5ec Oct 30, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Windows Windows-specific
Development

Successfully merging this pull request may close these issues.

None yet

3 participants