-
-
Notifications
You must be signed in to change notification settings - Fork 70
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 to Github Actions? #234
Comments
I have different behavior when I use It is failing with shell commands, but not with |
Why we are not using |
I'm not sure I understand what you're asking? |
Sorry Jon. After digging, I found the answer. I was worried we were running multiple time I am still playing with Github Actions. I found that running require "rspec"
require "rspec/core/rake_task"
RSpec::Core::RakeTask.new.run_task(false) On Github actions produce this warning:
|
Ok, the warning is produced by require 'rake'
require 'rake/tasklib'
system("#{Rake::TaskLib::RUBY} -e 'p :foo'") |
Ok we gonna to move this subject a little bit faster if TravisCI drop OSS. ATM I have issues on basic rspec-core project. Here is the config file. https://github.com/benoittgt/actions_ruby_testing/blob/master/.github/workflows/ruby.yml And a CI result https://github.com/benoittgt/actions_ruby_testing/runs/1343435673 |
It seems we can migration to travis-ci.com and use the free 10000 credits, but I'm not sure how much that would give us, as travis-ci.org was taking hours and hours during the release process for 3.10 I started investigating over here: https://github.com/rspec/rspec-core/tree/experimental-github-actions I got rspec-core passing on 2.5 2.6 and 2.7 but none of the earlier versions, so I started looking at how to deal with older Ruby versions. |
Just checked
At least you can go to the red zone ;D Circle is out from my point of view. |
For more ruby version I think we should switch to https://github.com/ruby/setup-ruby for example https://github.com/rspec/rspec-core/runs/1343995732 Ruby switch seems good... but I still have the resolve issue of
|
There is no 3.10.0pre, you have stale repos. |
You may find this handy if you don't already have this open :D https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/migrating-from-circleci-to-github-actions |
GA claim they allow for up to 20 concurrent jobs on a Free plan. |
I have MRI ruby running for |
Yeaah. I spend 3h yesterday trying to understand why ubuntu-latest was failing. I also read the discussion ruby/setup-ruby#100 Do we keep MRI preview on Travis or do we switch to head and allow failures? |
We will keep MRI preview on travis or an alternative unless we can convince them to support released preview versions. We will no doubt have the same problem with We also run head anyway and I have already configured allow failures. |
TravisCI is very slow to start. I started to work on the Github Action config for rspec-rails: https://github.com/rspec/rspec-rails/tree/github-actions As always feel free to push on my branch if you want to contribute to what I have started. :) |
Its hugely slow due to their "migration" e.g. they are resource starving it. |
According to https://www.traviscistatus.com/#month Some background: https://travis-ci.community/t/builds-hang-in-queued-state/10250/5
https://travis-ci.community/t/org-to-com-migration-deadline/10260
So I guess we'll have to wait for the migration to happen and re-evaluate the idea of moving to GHA basing on effect/effort. With GHA I can foresee some problems with e.g. checking out other repos, but they have an interesting approach to this https://github.com/marketplace/actions/github-action-build-chain-cross-repo-builds |
In my experimental branch we have no difficulty checking out other repos, it just works, I have Ruby 2.3 - 3.0 working, just missing JRuby and legacy Rubies. I'm going to be opening PRs over the weekend to move the majority of our builds across. |
For |
You might want to try latest ruby/setup-ruby (there were some fixes related to |
Wondering if this line may cause this error:
Locally:
|
Thanks. Both of you for your answer. It is much better now without |
Ok part of the CI is now green. https://github.com/rspec/rspec-rails/runs/1403770340?check_suite_focus=true Still work to do with JRuby and an issue with mailer loading + a small fix with Ruby 3. Then I will add other rails versions we support. I have the same issue on the WIP branch for rails 6.1 rspec/rspec-rails#2400 |
JRuby is failing on GHA for core too |
Todo:
Optional?:
|
rspec-rails for MRI is nearly ok. Moving to jruby brings to many issues ATM. Few of them related to mail gem and ActionMailer. https://github.com/rspec/rspec-rails/actions/runs/371123305
I am wondering if we should keep Github Actions for RSpec 4. Do not work on something that we will drop or do not use that much? |
We do use it so much though, it's taking hours for Travis to run, delaying PRs immensely. I'm not sure how much effort I'll put in but I'm keen to ditch Travis ASAP. |
Sorry my message was not clear. I am wondering how much effort we should invest on "docker images for legacy builds (pre 2.1)" ? |
I'm replying to that part... |
Closing because this is mostly done 🎉 |
Hello
I saw few recent OSS projects that move to Github Actions. I did a very basic try with rspec-core and only with MRI at the moment.
https://github.com/benoittgt/rspec-core/commit/70abad7b1d3fbdd21d9270e09a07a1fbc397df7c/checks?check_suite_id=392910092
For the moment I do not see a big improvement. Also I had to do ugly things to make the build green quickly.
The config for rspec-rails will be more complex.
To be honest I think it is maybe too early to move. I do no see a gain in execution time and debugging for the moment.
This issue is not a real one. I just open a discussion. I am also curious if you think we should switch to Github Actions.
Closing because it is only a discussion.
The text was updated successfully, but these errors were encountered: