CodeClimate report not showing in merge request

I am trying to activate the code climate report for merge requests pipelines in GitLab. The CodeClimate analyser is running but there are not shows any warnings when I add some bad code. There might be some configuration which I have missed.

I have added the following to my .gitlab-ci.yml file in the project rot folder:

    - template: Code-Quality.gitlab-ci.yml

And I have added the .codeclimate.yml file looks like this:

    enabled: true
      check: all
      language: c++
        - c++14
        - c++17

The build job completes with the following lines at the end of the log:

f47a75dcba39: Pull complete
Digest: sha256:c8afb8c2037f7b9c5c9ae198aff00b1cf80db11d3591fbe89dfb3c69192663f1
Status: Downloaded newer image for codeclimate/codeclimate:0.72.0
WARNING: A new version (v0.85.3) is available. Upgrade instructions are available at:
Uploading artifacts...
gl-code-quality-report.json: found 1 matching files 
Uploading artifacts to coordinator... ok            id=227197201 responseStatus=201 Created token=4xyzSXzN
Job succeeded

What could be wrong here, since the merge request doesn’t show any CodeClimate report?

In GitLab I have created one merge request with the configuration change (merging into master). And one merge request with some bad code, based on the first merge request with the configuration (merging into master).

The bad code:

int non_used_int;

int non_initialized_int;

int dummy = non_initialized_int;

// empty for loop
for (int i=0; i<100; i++) {


And a final note: I am using the shared GitLab runners provided by GitLab.

Guides I have followed:

I ran into the same issue when I ran my Code Quality test too. It said it archived an artifact but it’s nowhere to be seen. I wonder if you have to add json to an artifacts section of the .gitlab-ci.yml file.

From the documentation page:

By default, report artifacts are not downloadable. If you need them downloadable on the job details page, you can add gl-code-quality-report.json to the artifact paths like so:

  - template: Code-Quality.gitlab-ci.yml

    paths: [gl-code-quality-report.json]

Hi @frakman, yes you need to define a path for the report and be sure to add the test stage in your gitlab-ci.yml file as well. The report can be found on the job page then as a downloadable artifact and if the MR introduces code quality changes the differences will appear in the MR widget if a comparison of reports can be done.

One other thing to note is that this feature is available in starter / bronze or higher plans but not free plan as of Nov 2019.

Hopefully this gets you going with code quality.