You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "AThomsen (via GitHub)" <gi...@apache.org> on 2023/02/21 08:04:19 UTC

[GitHub] [incubator-devlake] AThomsen commented on issue #2604: [Feature][Azure Devops] Support Azure DevOps

AThomsen commented on issue #2604:
URL: https://github.com/apache/incubator-devlake/issues/2604#issuecomment-1438009044

   >... My question is, for the sake of DORA, should we be targeting only release deployments in our data collections, or can pipeline builds also potentially trigger deployments (perhaps not by Azure standards per se)? cc @hezyin
   
   I can answer that one, as @KasperSJensen and I are working on the same.
   
   Azure Devops has two ways of deploying. The "classic"/legacy way where release is its own entity. And the newer multi-stage yaml-pipelines. [Here's](https://stackoverflow.com/questions/59141250/azure-devops-multistage-pipeline-or-release-when-to-use-what) a SO thread discussing the two.
   
   Ideally both should be supported by DevLake, but yaml-pipelines should have priority as that is the way going forward.
   
   Actually, [Github Actions is forked from Azure Pipelines](https://learn.microsoft.com/en-us/dotnet/architecture/devops-for-aspnet-developers/actions-vs-pipelines) (yaml-pipelines) so perhaps the implementation can be based on that.


-- 
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: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org