Configure eslint job to output Code Quality report
All threads resolved!
All threads resolved!
Compare changes
eslint
to create JSON reports that GitLab Code Quality can import.Note: the formatter only creates a report file if it detects that the process is running in CI. (It does this by looking for CI-related env vars.) This means that non-CI-based eslint
runs are not affected and do not create such a file.
The functionality is demonstrated in a separate MR: !168587 (closed). That MR includes breaking a few lint rules to show that the report is successfully generated.
The report can be seen in a few places:
MR widget:
MR Changes (diff) view:
Dogfood new direction for Code Quality in gitla... (#382153 - closed)
This is part of replacing CodeClimate-based scanning with direct usage of scanning tools. Dogfooding this approach will help accelerate the transition for customers.
Documentation will soon include these specific steps: Docs: Add catalog of common tools integrated wi... (!172633 - merged).
Consider the effect of the changes in this merge request on the following:
gitlab-foss
security
dev
If new jobs are added:
This will help keep track of expected pipeline time and cost increases.