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

Replace Coveralls with SimpleCov #239

Merged
merged 1 commit into from
Jan 28, 2022
Merged

Replace Coveralls with SimpleCov #239

merged 1 commit into from
Jan 28, 2022

Conversation

dmagliola
Copy link
Collaborator

We've been having errors in CI from Coveralls, when trying to upload results.
(As mentioned in this comment)

This error seems to be because our coveralls gem is pretty old and abandoned,
and probably using a TLS version that is no longer supported.

(Reference: lemurheavy/coveralls-ruby#163)

One option recommended in that issue is to switch to a different coveralls-ruby-reborn gem.

However, given that we only use coveralls to upload results to the cloud,
only so we can have a badge in our README reporting 100%, in the interest of
security, I think i'd rather get rid of coveralls altogether, and use
simplecov directly instead, which reports the coverage when running the
tests and doesn't upload them anywhere.

We've been having errors in CI from Coveralls, when trying to upload results.
(As mentioned in [this comment](#230 (comment)))

This error seems to be because our coveralls gem is pretty old and abandoned,
and probably using a TLS version that is no longer supported.

(Reference: lemurheavy/coveralls-ruby#163)

One option recommended in that issue is to switch to a different `coveralls-ruby-reborn` gem.

However, given that we only use `coveralls` to upload results to the cloud,
only so we can have a badge in our README reporting 100%, in the interest of
security, I think i'd rather get rid of `coveralls` altogether, and use
`simplecov` directly instead, which reports the coverage when running the
tests and doesn't upload them anywhere.

Signed-off-by: Daniel Magliola <dmagliola@crystalgears.com>
@dmagliola
Copy link
Collaborator Author

@Sinjo @SuperQ what do you think?

Should we move to coveralls-ruby-reborn, which I don't know much about?
Or should we get rid of that badge and stop using coveralls entirely?

Is there any other use than that badge for coveralls.io?

@dmagliola dmagliola requested review from Sinjo and SuperQ January 7, 2022 00:26
Copy link
Member

@Sinjo Sinjo 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 +1 on this. I don't think the README badge is worth fighting poorly-maintained Ruby gems.

It might be nice for us to do something more with the report, but we can do that elsewhere.

@dmagliola dmagliola merged commit 582dbc3 into master Jan 28, 2022
@dmagliola dmagliola deleted the replace_coveralls branch January 28, 2022 09:16
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.

2 participants