Stop starting. Start finishing.
- David J. Anderson.

Deployment Frequency helps identify the rate at which you are delivering new business value to your customers. Smaller deployments have less risk of going wrong and provide an opportunity to deliver value to your customers in shorter iterations, allowing you to learn quicker.

In this article we'll be looking into:

1. How to Configure Deployments (Deployment Frequency)
2. Common Questions

Deployments

Step 1: Go to Settings

Click on the 'Settings' tab in the left sidebar to open up Haystack settings.

Step 2: Go to Settings > Configure Metrics

Click on 'Configure Metrics' in the left sidebar. And then click the 'View configuration' button under the 'Deployment Frequency' card.

Step 3: Select the repository you want to track for Deployment

You can select the repository to configure or you can click the `Configure All` button to configure the same settings for all repositories.

Step 4: Select the method you want to track for Deployment

After clicking configure button next to the repository you will be redirected suggestions section to select any predefined configuration that fits your organization.

You can either select any predefined suggestion or click the custom config option to select your own method.

After selecting custom configuration, click on the first dropdown. There are 8 options you can choose to calculate Deployment Frequency.

Option 1: git tag

Any commit that has been tagged by git tag or Github Releases will be counted as a single deployment.

We recommend teams to use git tags because it allows CI tools, deployment automation tools, and manual entering, granting different teams with different processes a standardized method.

Option 2: git tag contains

Any commit that has been tagged by git tag or Github Releases and fits a contains a certain string that you configure will be counted as a single deployment.

ex: to track "v1.2.3-prod", you can set the git tag containing rule as prod

Option 3: git tag not contains

Any commit that has been tagged by git tag or Github Releases and does not contain a certain string that you configure will be counted as a single deployment.


Option 4: merged into branch

Any pull request with the HEAD set as X will be counted as a single deployment.

ex: "master", "release", etc.

Option 5: merged into branch containing

Any pull request with the HEAD containing X will be counted as a single deployment.

ex: "master", "release", etc.

Option 6: containing title branch
Any pull request where the pull request title contains set as X will be counted as a single deployment.

ex: "Release", "deployment", etc.

Option 7: containing label

Any pull request which has label X will be counted as a single deployment.

ex: "release", "deployment", etc.

Option 8: each commit on default branch

Any commit that is on the default branch will be counted as a single deployment.

Step 5: That's it!

The changes might take a few minutes to calculate. Go back to deployments page and see your organization's deployment frequency!

Common Questions

Does Haystack support different processes for different Repositories?

Yes, you can track each repositories' Deployment Frequency using different rules. All you need to do is click on the `Configure` button next to each repository.

How do I select multiple terms in Pull Request Title?

Haystack supports multiple terms for Deployment Frequency. Note that you'll need to press enter after each term.


If you require further assistance, contact [email protected] or chat to us through the chatbot. We have helped 100+ engineering leaders track these data, and would be happy to share our expertise.

Check the following blogs:

Did this answer your question?