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
Move CI to GitHub Actions #176
Comments
First step to move the build to GitHub Actions: move the coverage generation from Travis to Actions. It doesn't generate additional information with lcov anymore, and now always runs on the latest available Ubuntu. [ci skip]
The following modifications were needed: - Use the GitHub Action codecov/codecov-action - Rename the workflow from codecov.yml to code-coverage.yml, otherwise the Codecov Action things it is the Codecov configuration file - Change codecov.yml to ensure that the test files are not covered [ci skip]
This commit also comments the Travis CI MacOS configurations, because they there too slow to run to completion anyway. [ci skip]
This commit is hopefully the last to get things to work with MacOS builds. Compared to the old Travis CI builds, we don't have Valgrind builds, but we have g++, ubsan and asan ones, which is more coverage than what we used to have. [ci skip]
Forgot to mention it, but commit 1de7526 add a workflow for Ubuntu. |
I got the following kinds of builds working:
While a bit different from the old Travis CI builds, I believe that I cover an equivalent amount of possibilities. There main differences are as follows:
This is pretty satisfying as everything runs smoothly. There are a few additional steps before closing the issue:
|
- Remove the license badge, redudant with GitHub UI - Better text for release and Conan badges - Remove the Travis CI badge - Add build badges to the compiler support section - Update the information about supported compilers
Considering that the build times are currently decent even with a full rebuild, I consider that making the workflows more complicated is not worth my time. I might give it another try in the future once features and usages have evolved, but currently it's got more cons than pros. As such, I consider that this issue is in a good enough state for now, and ready to ship. |
I planned to move the continuous integration to GitHub Actions at some point, but the recent changes to Travis CI mean that we will likely have to move sooner rather than later.
The text was updated successfully, but these errors were encountered: