[Question][Azure DevOps deployment] Azure DevOps deployment metrics configuration via devlake UI and scope config guide

[veetmoradiya3628]

Question

1. My use case is where azure pipelines code is there in the GitHub while pipeline runs / builds happening via Azure Dev Ops, does Dev lake support configuration for this use case, if so can someone please help with the configuration.
2. what is the best use of this scope configuration regex, here its not so clear (https://devlake.apache.org/docs/Configuration/AzureDevOps/#step-3---adding-transformation-rules-optional)

[dosubot[bot]]

To configure DevLake for Azure Pipelines hosted in GitHub with builds running in Azure DevOps, you can use regular expressions (regex) to define deployments in the scope configuration. Here's how you can set it up:

1. Configuration Support: DevLake supports your use case where Azure Pipelines are hosted in GitHub, and the builds are executed via Azure DevOps. You can configure DevLake to recognize these pipelines by setting appropriate regex patterns in the transformation rules.

2. Scope Configuration Regex: Use regex to match the names of Azure pipelines or job display names associated with the pipeline run. For example, if your deployment pipeline is named 'build-and-push-image', you can use the regex (push-image). To ensure case insensitivity, include (?i) before the regex, like (?i)(push-image).

   • Production Environment: For classifying deployments within the production environment, use a regex that matches the pipeline run's name or any job display names. For instance, if the deployment pipeline is named 'build-to-prod', you can use the regex (prod), and for case insensitivity, use (?i)(prod).

This setup is particularly useful for measuring DORA metrics, as it allows you to specify conditions under which a pipeline run is marked as a 'Production Deployment' ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.