diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 12:10:06 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-28 12:10:06 +0300 |
| commit | 8ce5735a199949ad19db9e83544875cd81562c69 (patch) | |
| tree | d552cb10b20be7d301adc094f770f76a1528de80 /doc/user/analytics | |
| parent | e9a3e8b891637a79ff6cc5bef9762272f312f04d (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/analytics')
| -rw-r--r-- | doc/user/analytics/dora_metrics.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/analytics/dora_metrics.md b/doc/user/analytics/dora_metrics.md index 6b7b1d87843..bdfeffcec05 100644 --- a/doc/user/analytics/dora_metrics.md +++ b/doc/user/analytics/dora_metrics.md @@ -43,7 +43,7 @@ High deployment frequency means you can get feedback sooner and iterate faster t ### How deployment frequency is calculated In GitLab, Deployment frequency is measured by the average number of deployments per day to a given environment, based on the deployment's end time (its `finished_at` property). -GitLab calculates the deployment frequency from the number of finished deployments on the given day. +GitLab calculates the deployment frequency from the number of finished deployments on the given day. Only successful deployments (`Deployment.statuses = success`) are counted. The calculation takes into account the production `environment tier` or the environments named `production/prod`. The environment must be part of the production deployment tier for its deployment information to appear on the graphs. |