The median amount of time for a commit to be deployed into production.
This metric measures the time it takes to commit code to the production environment and reflects the speed of software delivery. A lower average change preparation time means that your team is efficient at coding and deploying your project.
N/A
This metric can be calculated in two ways:
deploy-1
, deploy-2
deployed three new commits commit-1
, commit-2
and commit-3
.commit-1
is linked to pr-1
, commit-2
is linked to pr-2
and pr-3
, commit-3
is not linked to any PR. Then, deploy-2
is associated with pr-1
, pr-2
and pr-3
.Deploy-2
's lead time for changes = average cycle time of pr-1
, pr-2
and pr-3
.deploy-1
, deploy-2
deployed three new commits commit-1
, commit-2
and commit-3
.commit-1
, commit-2
and commit-3
is linked to any PR.deploy-2
‘s deployed_at - commit’s authored_dateDeploy-2
's Lead time for changes = average lead time for changes of commit-1
, commit-2
and commit-3
.Below are the benchmarks for different development teams:
Groups | Benchmarks |
---|---|
Elite performers | Less than one hour |
High performers | Between one day and one week |
Medium performers | Between one month and six months |
Low performers | More than six months |
Data Sources Required
This metric relies on deployments collected in multiple ways:
Transformation Rules Required
This metric relies on the deployment configuration in Jenkins, GitLab or GitHub transformation rules to let DevLake know what CI builds/jobs can be regarded as deployments.