GitLab Release Stage, 25 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.11 - Track DORA 4 lead time for changes metric

Description

Measuring the efficiency of your software development lifecycle is an important step to grow DevOps adoption for any organization. In the previous milestone, we added API support for lead time for changes at the project level. These metrics give you an indication of throughput so you know how long it takes for code to be committed and deployed to your production environment. In this release, you can now access this capability in the GitLab UI through the CI/CD dashboard, where a new graph will show the lead time for changes with the ability to view different time ranges, such as the last week, last month, or the last 90 days. In addition to the new graph, we have also added support for this API on the group level, allowing you to get aggregated lead time for changes metrics from all the projects that belong to the group.

A

Hi, my name is it's and I'm a senior technical marketing manager here at gitlab, and today I want to walk you through a new doraform network we introduced in gitlab 13.11.

A

We introduce a new graph for lead time for changes, but before we see this graph, let's understand what is door 4. So in order to measure, if your elite devops performer, the devops research and assessment, dora team has identified four key metrics that indicate performance of software development team deployment frequency. How long an organization successfully released to production lead time for changes the amount of time it takes a committee to get into production change, failure rate the percentage of deployment causing a failure in production and the last one is time to restore service.

A

How long it takes an organization to recover from a failure in production. So those are the four door metrics and in gitlab we already have two of them deployment, frequency and lead time for changes.

A

As you probably know, in github working iterations means that in each release we are adding new small features to support a big functionality or a big feature, deployment frequency already implemented in the project level and group level, as an api, and also in in the ui for the project level lead time for changes, api for the project level added in gitlab 13.10 and in gitlab 13.11.

A

We added lead time for change api for the group level, as well as as a graph in the ci cd dashboard. So, let's see this graph, I will go to analytics ci cd and I say new tabs one is for the deployment frequency, and this is the new graph we added in gitlab 13.11.

A

This chart displays the median time between email, request being merged and deployed to production. This graph also supports different periods of time. Last week, last month and last 19 days, this dashed line shows periods with no deployments.

A

In addition to this new ui graph, as I mentioned, we have also apis for the time for change both for the project level and the group level in github documentation. You can find all info about the api, as well as a example request for the project level example response for the project level same for the group level example request and example, response the same api works both for deployment frequency and the lead time for change depends on your metric query parameter. So this is all what I have to update you today.

A

Thank you for watching bye.