Configure eslint job to output Code Quality report
What does this MR do?
This MR takes our existing eslint
job and pipes its output to a Code Quality artifact.
Output still shows up in the job log, but it now also shows up in the Code Quality widget and in the MR diff.
Note: For testing, this MR adds a few eslint violations. Those won't be merged. After the pipeline config is reviewed, I'll remove those to make the MR ready for approval.
Related issues
Checklist
Pre-merge
Consider the effect of the changes in this merge request on the following:
-
Different pipeline types - Non-canonical projects:
-
gitlab-foss
-
security
-
dev
-
personal forks
-
-
Pipeline performance
If new jobs are added:
-
Change-related rules (e.g. frontend/backend/database file changes): _____ -
Frequency they are running (MRs, main branch, nightly, bi-hourly): _____ -
Add a duration chart to https://app.periscopedata.com/app/gitlab/652085/Engineering-Productivity---Pipeline-Build-Durations if there are new jobs added to merge request pipelines
This will help keep track of expected pipeline time and cost increases.
Post-merge
-
Consider communicating these changes to the broader team following the communication guideline for pipeline changes
Edited by Connor Gilbert