Skip to content

Switch from Travis to GitHub Actions for CI#47

Open
cgunther wants to merge 1 commit into
diogob:masterfrom
cgunther:github-actions
Open

Switch from Travis to GitHub Actions for CI#47
cgunther wants to merge 1 commit into
diogob:masterfrom
cgunther:github-actions

Conversation

@cgunther
Copy link
Copy Markdown

@cgunther cgunther commented Oct 15, 2022

Travis stopped building for open source in June 2021.

I'm testing Ruby 2.4+ and activerecord 4.2+, using Rails's CI as a guide for which Ruby versions to test each activerecord version on. While this gem's gemspec supports Ruby 1.8+ and activerecord 3.1+, the older Ruby versions aren't installable on GitHub Actions, or crash, so they're not tested. Given their age, support should likely be dropped for them as compatibility will no longer be ensured if CI isn't testing them.

I'm using PostgreSQL 11 as v12 and newer use a larger precision for the distance returned when using selecting_distance_from, which fails a spec. Ideally the spec should be updated to not assert a specific precision, allowing larger precisions.

This'll highlight a regression in selecting_distance_from on activerecord 6.1+ when called directly on a geolocated model, as opposed to through a geolocated model, which I'll address in a follow up PR.

Thanks for the existing work on this gem!

Note: I suspect CI wont actually run until after this is merged, then it should run on the resulting merge commit, as well as future PRs. You can see the results of the CI run on my fork:
https://github.com/cgunther/activerecord-postgres-earthdistance/actions/runs/3254382136

Travis stopped building for open source in June 2021.

I'm testing Ruby 2.4+ and activerecord 4.2+, using Rails's CI as a guide
for which Ruby versions to test each activerecord version on. While the
gemspec supports Ruby 1.8+ and activerecord 3.1+, the older Ruby
versions with aren't installable on GitHub Actions, or crash, so they're
not tested. Given their age, support should likely be dropped for them
as compatibility will no longer be ensured if CI isn't testing them.

I'm using PostgreSQL 11 as v12 and newer use a larger precision for the
distance returned when using `selecting_distance_from`, which fails a
spec. Ideally the spec should be updated to not assert a specific
precision, allowing larger precisions.

This'll highlight a regression in `selecting_distance_from` on
activerecord 6.1+ when called directly on a geolocated model, as opposed
to through a geolocated model, which I'll address in a follow up PR.
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

Successfully merging this pull request may close these issues.

1 participant