Startrekzky commented on issue #5000:
URL:
https://github.com/apache/incubator-devlake/issues/5000#issuecomment-1519045877
My opinions:
1. Whether we should support these Azure CICD deployments from external
repos?
Yes, If the use case does exist, which means users have to collect the CICD
data triggered by external repos to measure DORA metrics by DevLake.
2. How I understand this phenomenon from the product level.
I treat Azure Pipeline as an independent CI/CD tool. That's why it enables
'triggering' from external repos just like Jenkins does. Actually, I'm curious
if GitLab CI shares the same problem.
3. How should we tackle it?
- Option 1 - Divide Azure DevOps to Azure Repos and Azure Pipeline: I guess
no one wants this way.
- Option 2 - Add external data scope to the option list of 'setting data
scope for an Azure connection', other configuration stays the same. If users
- only select internal Azure repos: everything stays the same
- select one or more external Azure repos: users cannot remove 'CICD
domain' in the Data Entities configuration. Since the external repos are not
collected by DevLake, the cicd_scope_id from external Azure repos can be marked
as the repo's own unique identifier.
4. What's the urgency?
I won't treat it as an urgent problem until 3+ users bring it to us on
GitHub or Slack.
@CamilleTeruel @hezyin @klesh @yumengwang03
--
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]
