realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/user/group/repositories_analytics/index.md
Pirate Praveen 98b945ec52 New upstream version 13.9.3+ds1
2021-03-11 19:13:27 +05:30

4.2 KiB
Raw Blame History

type stage group info
reference Verify Testing To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments

Repositories Analytics (PREMIUM)

Introduced in GitLab Premium 13.4.

WARNING: This feature might not be available to you. Check the version history note above for details.

Group repositories analytics

Current group code coverage

The Analytics > Repositories group page displays the overall test coverage of all your projects in your group. In the Overall activity section, you can see:

  • The number of projects with coverage reports.
  • The average percentage of coverage across all your projects.
  • The total number of pipeline jobs that produce coverage reports.

Average group test coverage from the last 30 days

The Analytics > Repositories group page displays the average test coverage of all your projects in your group in a graph for the last 30 days.

Latest project test coverage list

To see the latest code coverage for each project in your group:

  1. Go to Analytics > Repositories in the group (not from a project).
  2. In the Latest test coverage results section, use the Select projects dropdown to choose the projects you want to check.

Download historic test coverage data

Introduced in GitLab Premium 13.4.

You can get a CSV of the code coverage data for all of the projects in your group. This report has a maximum of 1000 records. The code coverage data is from the default branch in each project.

To get the report:

  1. Go to your group's Analytics > Repositories page
  2. Click Download historic test coverage data (.csv),
  3. In the popup, select the projects you want to include in the report.
  4. Select the date range for the report from the preset options.
  5. Click Download test coverage data (.csv).

The projects dropdown shows up to 100 projects from your group. If the project you want to check is not in the dropdown list, you can select All projects to download the report for all projects in your group, including any projects that are not listed. There is a plan to improve this behavior in this related issue.

For each day that a coverage report was generated by a job in a project's pipeline, there will be a row in the CSV which includes:

  • The date when the coverage job ran
  • The name of the job that generated the coverage report
  • The name of the project
  • The coverage value

If the project's code coverage was calculated more than once in a day, we will take the last value from that day.

NOTE: In GitLab 13.7 and later, group code coverage data is taken from the configured default branch. In earlier versions, it is taken from the master branch.