<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The `code_quality` check fails when using Ruby 2.6, as the Rubocop version being used does not support > Ruby 2.5. This is an allowed failure so the Pipeline doesn't fail -- but it does remove a bit of the 'it just works' feeling. We should upgrade Rubocop on whatever is running the `code_quality` check. Looks like anything > [0.60.0](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md#0600-2018-10-26) should work. ### Steps to reproduce 1. Create Ruby Project and upload to Gitlab 2. Enable Auto DevOps 3. Pipeline will run and code_quality check should fail. ### What is the current *bug* behavior? Code quality check fails when using Ruby 2.6. ### What is the expected *correct* behavior? Code quality check should execute when using Ruby 2.6. ### Relevant logs and/or screenshots  ### Possible fixes Upgrade to a newer version of Rubocop.