Commit b80a0450 authored by Shinya Maeda's avatar Shinya Maeda

ini

parent 55f63361
......@@ -527,7 +527,7 @@ karma:
- chrome_debug.log
- coverage-javascript/
codeclimate:
codequality:
<<: *except-docs
<<: *pull-cache
before_script: []
......
......@@ -37,7 +37,7 @@ module Ci
scope :with_expired_artifacts, ->() { with_artifacts.where('artifacts_expire_at < ?', Time.now) }
scope :last_month, ->() { where('created_at > ?', Date.today - 1.month) }
scope :manual_actions, ->() { where(when: :manual, status: COMPLETED_STATUSES + [:manual]) }
scope :codeclimate, ->() { where(name: 'codeclimate') }
scope :codeclimate, ->() { where(:name => %w[codequality codeclimate]) }
mount_uploader :artifacts_file, ArtifactUploader
mount_uploader :artifacts_metadata, ArtifactUploader
......
......@@ -5,10 +5,10 @@ GitLab CI and Docker.
First, you need GitLab Runner with [docker-in-docker executor][dind].
Once you set up the Runner, add a new job to `.gitlab-ci.yml`, called `codeclimate`:
Once you set up the Runner, add a new job to `.gitlab-ci.yml`, called `codequality` or `codeclimate`(DEPRECATED):
```yaml
codeclimate:
codequality:
image: docker:latest
variables:
DOCKER_DRIVER: overlay
......@@ -22,7 +22,7 @@ codeclimate:
paths: [codeclimate.json]
```
This will create a `codeclimate` job in your CI pipeline and will allow you to
This will create a `codequality` job in your CI pipeline and will allow you to
download and analyze the report artifact in JSON format.
For GitLab [Enterprise Edition Starter][ee] users, this information can be automatically
......
......@@ -28,7 +28,7 @@ For instance, consider the following workflow:
## How it works
In order for the report to show in the merge request, you need to specify a
`codeclimate` job (exact name) that will analyze the code and upload the resulting
`codequality` job (exact name) that will analyze the code and upload the resulting
`codeclimate.json` as an artifact. GitLab will then check this file and show
the information inside the merge request.
......@@ -38,11 +38,11 @@ Code Climate display in the merge request.
If the Code Climate report doesn't have anything to compare to, no information
will be displayed in the merge request area. That is the case when you add the
`codeclimate` job in your `.gitlab-ci.yml` for the very first time.
`codequality` job in your `.gitlab-ci.yml` for the very first time.
Consecutive merge requests will have something to compare to and the code quality
report will be shown properly.
For more information on how the `codeclimate` job should look like, check the
For more information on how the `codequality` job should look like, check the
example on [analyzing a project's code quality with Code Climate CLI][cc-docs].
[ee-1984]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1984
......
......@@ -112,7 +112,7 @@ describe Ci::Build do
create(
:ci_build,
:artifacts,
name: 'codeclimate',
name: 'codequality',
pipeline: pipeline,
options: {
artifacts: {
......@@ -130,7 +130,7 @@ describe Ci::Build do
create(
:ci_build,
:artifacts,
name: 'codeclimate',
name: 'codequality',
pipeline: pipeline,
options: {}
)
......
......@@ -1330,7 +1330,7 @@ describe Ci::Pipeline, :mailer do
create(
:ci_build,
:artifacts,
name: 'codeclimate',
name: 'codequality',
pipeline: pipeline,
options: {
artifacts: {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment