Deployment Frequency (Git Releases) KPI

Why Git Release Frequency Matters

• Accelerate Value Delivery: More frequent Git releases mean users get features and fixes sooner.

• Surface Process Bottlenecks: Spikes or dips in release counts highlight workflow inefficiencies.

• Improve Transparency: Sharing release cadence with stakeholders builds trust and alignment

How to Calculate Git Release Frequency

Release Frequency = 
  Total Number of Git Releases 
  / Number of Days in Period

(Opsera counts each Git “release” event—tag creation or GitHub Release—within your date range.)

Example

You tagged 15 releases over 30 days → Frequency = 15 / 30 = 0.5 Git releases per day

How Opsera Helps You Track Git Release Frequency

1. Overview Chart

   • Visualize your release count over time for the current, previous, and two-period-ago windows.

2. Trend Chart

   • Click any point to drill into the specific release’s metadata: name, tag, created vs. published time, deployment duration, author, and a link to details.

3. List of Releases Table

   • Comprehensive table with columns for Release Name, Tag, Created Time, Published Time, Deployment Time, Author, and Release Link—filterable for quick triage.

4. Group Mappings & Filters

   • Define a Group Mapping in Insights NX → Tools & Mapping to filter by Project URL or other attributes. Then apply date-range and tag filters for focused views.

Best Practices

• Standardize Release Tags: Use clear semantic versioning (e.g. v1.2.3) so your charts and tables remain meaningful.

• Automate Release Creation: Leverage CI steps to auto-tag and draft GitHub Releases, ensuring consistency.

• Filter Noisy Repos: Exclude non-product repos (infra, docs) via Group Mappings to keep your metric focused.

• Correlate with DORA Metrics: Compare Git Release Frequency alongside Deployment Frequency and Lead Time for Changes for end-to-end delivery insights.

FAQ

1. What counts as a “Git release”? Any Git tag or GitHub Release event your pipeline emits during the selected period.

2. How do I set up Group Mappings?

3. In Insights NX → Tools & Mapping → Groups, click + New Group, choose your filters (e.g. Project URL), then save. Apply this group when viewing the KPI.

4. Can I include draft or prereleases? Yes—use the Status filter on the Release List table to include drafts, prereleases, or only full releases.

5. How often does the data update? In real time—as soon as a Git release is published, the Overview chart, Trend chart, and table refresh automatically.

6. Can I export the release list? Yes—download the List of Releases table as a CSV or share its dashboard link with your team.