warren830 opened a new issue, #2604:
URL: https://github.com/apache/incubator-devlake/issues/2604

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   # Phase 1 - Integrate Azure Pipelines (DONE)
   
   ### Description
   
   According to issue https://github.com/apache/incubator-devlake/issues/2537 , 
  we need to investigate [Azure 
Pipelines](https://azure.microsoft.com/en-us/products/devops/pipelines/) to 
design DevLake's CICD domain schema.
   
   ### Use case
   
   As DevLake's engineer, I need to investigate Azure Pipeline's data models. 
We'll compare these with other CI/CD tools such as Jenkins, GitLab CI and 
GitHub Action, then we can work on 
https://github.com/apache/incubator-devlake/issues/2537 to design a better CICD 
domain layer model in DevLake. 
   
   See the up-to-date [CICD domain layer 
model](https://devlake.apache.org/docs/next/DataModels/DevLakeDomainLayerSchema#domain-4---cicdwip)
   
   
   # Phase 2 - Integrate Azure Repos (v0.16)
   
   According to the comments under this ticket, many Axure DevOps users want to 
measure DORA metrics. Most of them use  [Azure 
Repos](https://azure.microsoft.com/en-us/products/devops/repos/) for source 
code management and code review. To calculate DORA metrics, we have to collect 
these entities from Azure DevOps, which includes:
   
   - [source code management 
entities](https://devlake.apache.org/docs/next/DataModels/DevLakeDomainLayerSchema#domain-2---source-code-management):
 repos, refs, commits, commit_files, etc.
   - [code review 
entities](https://devlake.apache.org/docs/next/DataModels/DevLakeDomainLayerSchema#domain-3---code-review):
 prs, pr_comments, etc.
   
   This is a video introduction of [Azure 
DevOps](https://www.youtube.com/watch?v=JhqpF-5E10I)
   
   # Phase 3 - Add configuration and config-ui for Azure DevOps (v0.16) 
(Tracked in #3321)
   
   ### Backend
   Apart from the existing configuration of Azuer pipeline entities, the 
backend should offer at least 1 more configuration: `PR and issue association`: 
to parse Axure's own issues or Jira issues from Azure PR bodies and associate 
them in table.pr_issues, similar to what we did in GitHub.
   
   
![image](https://user-images.githubusercontent.com/14050754/207678241-9a787711-a36e-46a0-9735-72e9a90f6e7c.png)
   
   ### Frontend
   Add Config-UI for Azure DevOps. This will be tracked in #3321 
   
   
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to