-
Notifications
You must be signed in to change notification settings - Fork 529
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
Use GitHub Action instead of travis-ci.org #515
Conversation
CI doesn't work against recent PRs because building on travis-ci.org is ceased. We can use travis-ci.com instead of travis-ci.org, but it has limitations to build time. So I think using GitHub Actions is the best CI to build this repository. I migrated the settings while maintaining the original state as much as possible. Improvements to the configuration, such as adding Rails 7.0, will be done in the next PR.
You can check the test results of this PR here. Use GitHub Action instead of travis-ci.org · willnet/paranoia@5689e21 |
.github/workflows/test.yml
Outdated
|
||
jobs: | ||
test: | ||
runs-on: ubuntu-latest |
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.
20.04 sounds a better bet for something aimed at servers
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.
good point!
changed at 11908cd
- 2.3.8 | ||
- 2.4.5 | ||
- 2.5.3 | ||
- 2.6.3 |
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.
shall we take the opportunity to remove 2.3, and 2.4, add 2.7 and 3.0 ?
separate PR is better?
- ruby-version: '2.4.5' | ||
gemfile: rails_6_0 | ||
- ruby-version: '2.4.5' | ||
gemfile: rails_6_1 |
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 think that was neat how they made it work with ENV vars for travis. it should be possible to keep the same pattern with github actions, at least that's what I am trying
👍 on switching to Github actions. Run build is here https://github.com/willnet/paranoia/actions/runs/1302894789 All test pass ! shall we remove the |
Alternative #516 |
CI doesn't work against recent PRs because building on travis-ci.org is ceased.
We can use travis-ci.com instead of travis-ci.org, but it has limitations to build time. So I think using GitHub Actions is the best CI to build this repository.
I migrated the settings while maintaining the original state as much as possible. Improvements to the configuration, such as adding Rails 7.0, will be done in the next PR.