Move legacy Ruby builds from CircleCI to GitHub Actions #155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattbrictson
force-pushed
the
chores/move-legacy-ruby-ci-to-actions
branch
2 times, most recently
from
8a6f8ac
to
6a99174
Compare
mattbrictson
force-pushed
the
chores/move-legacy-ruby-ci-to-actions
branch
from
6a99174
to
6cb6185
Compare
mattbrictson
force-pushed
the
chores/move-legacy-ruby-ci-to-actions
branch
from
c164f75
to
9a1bfdf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For testing legacy versions of Ruby at CircleCi, we rely on the official Ruby Docker images. The
ruby:1.9image is now so old that the latest version of the Docker Engine does not support it. As a result, CircleCI builds are now failing.Fix this by switching from CircleCi to GitHub Actions for testing legacy Ruby versions. In the Actions workflow, we use
setup-rubyto install the desired Ruby version, rather than rely on the problematic Docker image.