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

Drop integration tests for Ruby 2 and Rails 5 #160

Merged
merged 6 commits into from
Aug 23, 2024

Conversation

mec
Copy link
Member

@mec mec commented Aug 23, 2024

Supporting these is more effort than value so we will drop support.

This work only relates to our integration tests and not the gem itself.

@coveralls
Copy link

coveralls commented Aug 23, 2024

Pull Request Test Coverage Report for Build 10523965758

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 9171164056: 0.0%
Covered Lines: 393
Relevant Lines: 393

💛 - Coveralls

Whilst we generally pass this argument, it should be `2.0.0`.
@mec mec force-pushed the chore/drop-ruby-2-and-rails-5-int-testing branch from 89a8669 to 9a3cf45 Compare August 23, 2024 08:27
@mec mec changed the title chore/drop ruby 2 and rails 5 int testing Drop integration tests for Ruby 2 and Rails 5 Aug 23, 2024
We are dropping integration test support for these end of life versions.

This work will focus solely on the integration tests and not the gem
itself.
@mec mec force-pushed the chore/drop-ruby-2-and-rails-5-int-testing branch from 9a3cf45 to 10f676e Compare August 23, 2024 08:32
@mec mec marked this pull request as ready for review August 23, 2024 08:39
Copy link

@yndajas yndajas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not confident reviewing the last commit, but the rest look good to me

.github/workflows/rails-integration-tests.yml Show resolved Hide resolved
run: |
rails_versions=$(curl https://rubygems.org/api/v1/versions/rails.json | jq 'group_by(.number[:1])[] | (.[0].number) | select(.[:1]|tonumber > 5)' | jq -s -c)
rails_versions=$(curl https://rubygems.org/api/v1/versions/rails.json | jq '[.[] | select(.number | test("beta") | not)] | group_by(.number[:1])[] | (.[0].number) | select(.[:1]|tonumber > 5)' | jq -s -c)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know the jq syntax well enough to review this line

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, me too, I would prefer something less dynamic but more obvious, but happy to trust in this having seen it work.

@@ -45,7 +45,7 @@ COPY --from=build /rails /rails
WORKDIR /rails/mail-notify-integration

# add Mail Notify to the Gemfile
ARG MAIL_NOTIFY_BRANCH=v2
ARG MAIL_NOTIFY_BRANCH=2.0.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you say "we generally pass this argument", do you mean it gets passed in somewhere else, overriding this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, when you build a docker image you can pass in arguments to change the output, it's a common pattern to declare and set a default like this, you see it a lot in this Dockerfile. ARG for images ENV for running containers.

We are dropping support for Rails 5 in our integration tests.
@mec mec force-pushed the chore/drop-ruby-2-and-rails-5-int-testing branch from 10f676e to 0f1f10d Compare August 23, 2024 10:12
@mec mec merged commit fe2cc63 into main Aug 23, 2024
15 checks passed
@mec mec deleted the chore/drop-ruby-2-and-rails-5-int-testing branch August 23, 2024 10:21
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.

3 participants