-
Notifications
You must be signed in to change notification settings - Fork 5
Complete move from Travis CI to GitHub Actions #20
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
Conversation
bcf6969
to
838f177
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.
Seems good 👍
No comments for workflow duplication as we already have an issue to deal with it.
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 agree with your comments. :)
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.
Looks good! Apply fixups and merge!
As last step before removing the Travis CI configuration we recreate the build process for executables of the command line tools. The executables are build for three target architectures - "x86-64" and "skylake" were also build by Travis CI - "x86-64-v3" is added since this target showed best performance for the Python bindings and most likely gives good performance for the command line tools as well.
Travis CI is not used anymore but GitHub Actions. With the recent changes the Travis CI workflow is reproduced by GitHub Actions. Therefore, we do not need to keep the outdated configuration files anymore. New releases on GitHub must be created manually. The pre-compiled command line tools need to be downloaded and then added manually to the release. The Python wheels are available on PyPI and are uploaded there automatically. Further automation of releases is possible, but we currently do not expect many releases to justify the creation and maintenance of such a job.
7b503fa
to
378dc13
Compare
No description provided.