Gitlab Pipelines : Lead Time for Changes

Owned by Aruna Pattabiraman (Unlicensed)
Aug 17, 2022
2 min read

Gitlab Lead Time for Changes measures three metrics,

  1. Average Lead Time - The average time it takes from Code Commit to Production Deployment. Production deployment stage can be defined as a part of KPI filters.

  2. Average Merge Time - The average time it takes from a Code Commit to complete a Merge Request.

  3. Lead Time split and count by days - Chart that shows by number of days, the count of commits that have been made, merged and deployed to production.

 

 

The KPI has a settings panel with the following capabilities:

  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.

Â