Feat: Use version of rubocop specified in gemfile

[kjg]

Would it be possible for codeclimate to use the same version of rubocop (and any rubocop extensions like ruboco-rspec) as specified in the projects Gemfile.lock (if it shows up there) so that the errors are the same in codeclimate as they would be locally?

[wyefei]

Are you guys working on this?

[rwadstein]

We have recently signed up for CodeClimate and are having the same issue. We recently were using HoundCi and with the switch to CodeClimate we are being forced to downgrade the version of rubocop in order to have the same results between local and CC. Also all of our configurations would have to go back to the old namespace.

[maxjacobson]

@rwadstein Hi there. Depending which version of RuboCop you're using outside of Code Climate, we may already support it via engine channels. We currently offer these channels:

• rubocop-0-42
• rubocop-0-46
• rubocop-0-48
• rubocop-0-49

And we're planning to add a rubocop-0-50 soon (see tracking issue)

Long-term we may do something more automatic than this, but for the time being, please pick the channel that you prefer and feel free to let us know when we're missing support for things that you need.

[rwadstein]

@maxjacobson Thank you for the info. Support had told me that last week and we addressed the issue on our side.. I should have come back to this issue in order to update it.

[maxjacobson]

Oh, glad to hear it 👍.

[coding-red-panda]

So is this idea ever going to happen?

[maxjacobson]

Hi @coding-bunny. Thanks for checking in. I'm not sure about ever, which is a long time, but for the time being, channels remain our solution to this problem.

[andi-dev]

Unfortunately It seems the rubocop channels do not get updated frequently - by now version 0.76 is released. And is there any supported way to get rubocop extensions to work?

Thanks in advance.

[coding-red-panda]

I've given up on running RuboCop through CodeClimate and made it part of our CI instead of the CodeClimate plugin.

[klyonrad]

Just saying this for your priorization: This is the number one reason why I would never ever take the paid plain. If my team were bigger than 4 I would build something on my own for Pull Request linting with pronto.

[klyonrad]

Also rubocop extensions should not be forgotten, mainly rubocop-rails.