Skip to content
GitLab
Next
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,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • #328772
Closed
Open
Issue created Apr 22, 2021 by Gerardo Gutierrez@gerardoDeveloper0 of 6 checklist items completed0/6 checklist items

Test coverage Visualization artifact size limit

Release notes

Customers utilizing Test Coverage visualization with a large code base, have a problem utilizing this feature due to the large file generated.

Problem to solve

Users with large code base, and large code testing should be able to use this feature and not limited by file limit.

Intended users

User experience goal

The user should be able to implement Test Coverage visualization and visualize the code coverage on their MR diff view

Proposal

Found a hard coded limit on the pipeline_artifact model. This value is set to 10MB. Current client is having issues due to their large code base, and generating file over 30MB. ZD 202429

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

What does success look like, and how can we measure that?

Being able to parse code coverage artifacts larger than 10MB, possible as large as 50-100MB.

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Workaround

Split you Cobertura XML file into many smaller files. See customer provided script on this comment

Edited Dec 06, 2021 by Gerardo Gutierrez
Assignee
Assign to
Time tracking