Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,058
    • Issues 44,058
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,304
    • Merge requests 1,304
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #358759
Closed
Open
Created Apr 12, 2022 by Connor Gilbert@connorgilbert🌴Developer

Investigation: Code Quality performance with multiple reports

The Code Quality feature currently supports ingesting multiple codequality artifacts. However, they only are usable in the MR widget, and can't be used in the full pipeline report (#9014) or in the diff view (#328257 (closed)).

A previous effort got to the feature-flag rollout stage, but was held back for backend performance reasons. #340525 (comment 752188789)

The goal of this issue is to investigate the current extent of the performance issues and system design to identify what steps we need to take to unblock the multiple-reports feature. The intended output could also include suggested system designs.

There are at least two internal use cases for this feature (#355051 (comment 877306046), gitlab-docs#1088) as well as those tagged onto the existing issues.

Edited Apr 12, 2022 by Connor Gilbert
Assignee
Assign to
Time tracking