dotnet / dotnet/arcade-services
Expand Build Analysis support to include the DevDiv AzDO instance
- Dominant language
- C#
- Stars
- 86
- Forks
- 86
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 35
Description
Migrated from Azure DevOps: https://dnceng.visualstudio.com/internal/_workitems/edit/7834 (DNCENG Task 7834)
## Summary
Some of our customers still run their builds on the **DevDiv AzDO instance** and would like to utilize Build Analysis. Currently, we only have service hooks set up to send build messages to the Build Analysis message queue on the **dnceng** and **dnceng-public** AzDO instances.
## Work to investigate / implement
- Investigate what work would be required to expand Build Analysis to support additional AzDO instances, including the effort to manage service hooks outside of our ability to directly admin.
- Check with VSEng for requirements to set up the necessary service hooks.
- Investigate how we can auth with the service hooks in DevDiv (assuming a federated credential, similar to what's on dnceng/dnceng-public).
- Implement necessary changes and verify everything works.
_Original area path: `internal\.NET Engineering Services` · Tags: Needs triage_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the existing Build Analysis service hooks for the dnceng and dnceng-public AzDO instances, then review the migrated DNCENG Task 7834 and check requirements with VSEng. Investigate federated-credential authentication for DevDiv and the process for managing its hooks; done means DevDiv build messages reach Build Analysis and the integration is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100