Deployment log shows you the deployments Flow uses to calculate DORA metrics. Use Deployment log to have conversations with your team about specific deployments to gain further insight.
Deployment log overview
Use Deployment log to add additional context to conversations about your deployment-based DORA metrics. In addition to seeing your overall DORA metrics, use this report to take a closer look at specific deployments affecting your metrics.
For example, if you have a lower Deployment frequency than you’d like, use Deployment log to see which teams and repos have deployments associated with them to understand who is deploying code and when it’s happening.
If Lead time for changes is higher than you’d like, use Deployment log to find the deployments with the highest Lead time for changes to have better conversations with your team on how to improve and what context is driving those numbers.
Note: If you use practices like squashing or rebasing that change the date of commits, your Lead time for changes will change to match the new commit dates.
Also use this report to pinpoint successful deployments so you can have further conversations about how to replicate success.
Which commits are included in a deployment?
All commits in a repository between the last included deployment and the next included deployment are counted toward a deployment. Commits from non-included deployments are automatically part of the next included deployment. This means the total number of commits in a deployment in Flow may not match what you see in your system, especially if you configure a deployment regular expression in Flow.
Before getting started
Using Deployment log
Tip: Deployment log does not appear in the list of Flow reports in the left navigation. Find Deployment log through Home or Retrospective.
Access Deployment log through the DORA metric widgets in Home and Retrospective.
In Home, under Deployment frequency or Lead time for changes, click View on, then click Deployment log.
In Retrospective, under Deployment frequency or Lead time for changes, hover over the bar graph and click View deployments.
If you don’t see the deployments you expect, click Edit configuration to go to the Repos page. From here, edit the deployment source for your repositories.
Deployment log shows you the name of the deployment, its date and time, the number of commits in the deployment, and the Lead time for changes calculated per deployment.
The teams column shows all teams in Flow with a team member who authored a commit in the deployment. If a Flow user is in multiple teams, all of their teams are listed.
The authors column lists all users who authored a commit in the deployment, as well as the user who applied the git tag.
Filtering in Deployment log
Use the team and date filters at the top of the report to select which data you’d like to view.
The Team filter shows only deployments that include a commit authored by someone on the team. The Date range filter shows only deployments made during that range.
Tip: If the Team column is blank, no commit authors from the deployment are part of a team in Flow. Make sure your users are all assigned to teams.
Once these filters are selected, click the column headers to sort the list of deployments in order by that header.
Click the repo name in the Repo column to view the repo in your own system.
Note: If you’re unable to access your repo from this page, you need to set up a Vendor URL template so Flow can correctly link to your git host.
If you need help, please contact Pluralsight Support.