-
Notifications
You must be signed in to change notification settings - Fork 76
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
Setup appveyor builds of binaries #90
Comments
Thanks for your suggestion! Where would I put these artifacts? |
Appveyor stores them itself (you only need to specify in appveyor.yaml what to store) and allows direct links to the artifacts from the latest build, if their name doesn't change from build to build. |
I don't have any appveyor.yaml, it's all configured in the web interface. It seems like there are three types of artefacts allowed:
There is also an "auto" option, but I don't know if that allows any other type of artefact? Which artifact is suitable for unshield? Octopus? Can you help me create a compatible artefact with CMake? |
Maybe it is possible to create a .msi package like this? |
Any types of artifacts are allowed. How to setup build you can see here: https://github.com/jpype-project/jpype/blob/devel/appveyor.yml (not a very good example, since some artifacts are uploaded manually rather than using |
Seems I could specify the .exe as an artifact! |
Maybe fixed by #105 |
|
Yet! :) |
I see this project has switched to GitHub Actions which does provide artifacts after logging in to GitHub (which means the issue is effectively solved) GitHub releases don't have any artifacts though (which makes things harder for Windows users) so there's still some work to do |
Yeah, what is missing is putting the artifacts somwhere permanent... |
Appveyor allows automatically building binaries after every commit and publishing artifacts.
The text was updated successfully, but these errors were encountered: