Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Gitlab Deployment Frequency measures the following metrics,

  1. Selected Stages - As a part of settings, users can select the appropriate deployment stages. This metric shows the number of stages selected.

  2. Average Deployment Frequency - For a selected date range, the average number of times the selected stages have been deployed. This is calculated based on (total number of times selected stages executed / total number of days selected).

    1. Smart Indicator Trend Icon : The trend icon indicates whether the average deployment frequency has increased / decreased based on the previous equivalent time range. For example, if this week is selected in the date settings, then the trend compares against the previous week results.

    2. Smart Indicator Previous Average : This previous average is calculated based on the previous time range results.

  3. Total Pipeline runs - This is the total number of times pipelines have been executed in a given period of time. The pipeline runs are based on the stages selected. The total pipeline runs are calculated only if the selected stages are part of the pipeline. There may be differences in the total pipeline runs and total deployments. This is due to the pipelines being run, but the deployment stage might have failed/skipped.

  4. Total Deployments - For the selected time range, this calculates the total number of times the selected stages have been executed.

The KPI has a settings panel with the following capabilities:

Settings

  1. Tags : (Currently disabled) supports all the project and application tags, and allows users to slice data into multiple dimensions/representations.

  2. Deployment Stage : Gitlab pipelines allow users to provide/define stages however they want. Hence in order to capture the correct stage name in the calculations, users will be able to provide the production deployment stage as an input, and the lead time will modify itself accordingly.

  3. Gitlab Projects : (Temporary) allows user to filter results based on list of projects.

  4. Date picker : To measure lead time, and average time to merge for a specific time range.

Data Point Settings

This is enabled for Average Deployment Frequency KPI, where users are allowed to set goals for the metric. The goals are split into three zones, Success, Warning and Failure, each having its own color indicators, and depending on that, the values will be shown in the UI.

There is a toggle which allows users to enable notifications for this Metric. More details can be fetched from How To : Enable GChat Notifications for GitLab Deployment Frequency KPI .

  • No labels