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

CI: GitHub Actions #361

Closed
tueda opened this issue Jul 17, 2020 · 2 comments
Closed

CI: GitHub Actions #361

tueda opened this issue Jul 17, 2020 · 2 comments

Comments

@tueda
Copy link
Collaborator

tueda commented Jul 17, 2020

Github Actions offer free 20 concurrent jobs , while Travis CI offers 5. Maybe some of the current CI jobs (for example Valgrind-related jobs), or all of them, could be moved from Google (Travis CI backbone) to Microsoft (GitHub Actions backbone), which gives us a speed gain in CI.

It is also possible to automatize generating documentation on GitHub.

@tueda
Copy link
Collaborator Author

tueda commented Sep 13, 2021

Now, travis-ci.org has been shut down...

tueda added a commit that referenced this issue Nov 1, 2022
- Test: build and test. It also measures code coverage to be uploaded to
  coveralls.io:

    https://coveralls.io/github/vermaseren/form

- Deploy: build binaries and manuals. These files are published to
  GitHub Releases if the commit has a versioning tag starting with "v".
@tueda
Copy link
Collaborator Author

tueda commented Nov 1, 2022

I have set up GitHub Actions with 2 workflows. Test is for building and testing with measuring code coverage to be uploaded to coveralls.io. Deploy is for building binaries and generating manuals, which will be published to GitHub Releases when the commit has a versioning tag starting with v, for example, v4.2.2 or v5.0.0.

Some notes:

In the next commit, I will remove the remaining files related to Travis CI and close this issue.

tueda added a commit that referenced this issue Nov 1, 2022
- The status badge in README now links to GitHub Actions.
@tueda tueda closed this as completed Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant