search

dotnet / arcade

Tools that provide common build infrastructure for multiple .NET Foundation projects.
MIT License
671 stars 347 forks source link

Automation to create tracking issues back from Azure DevOps #8567

Closed riarenas closed 2 years ago

riarenas commented 2 years ago

With the migration of issue management from core-eng to Arcade, there are certain categories of issues that should not have their implementation details in the open. and should instead be work items in Azure DevOps, along with a tracking link in GitHub for work tracking purposes. This poses a certain overhead to individual devs, as they need to keep track of both issues and make sure they are assigned to the correct epics.

We should be able to build some automation that scans these backing issues that we create in Azure DevOps and creates the tracking github issues. This would both help the individual dev only manage the source of truth for the work, and make sure things are being properly tracked in Arcade.

michellemcdaniel commented 2 years ago

I am going to model the structure of this after the BuildAnalysisProcessor, using the storage queue azdo service hooks, since we don't really need it to be exactly in real time, and that fails less than the webhooks processor stuff does.

michellemcdaniel commented 2 years ago

PR: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/21697

michellemcdaniel commented 2 years ago

It's opening issues now, but it's failing to add the epic issue because of auth issues with the github graphql api which.... doesn't make sense.

michellemcdaniel commented 2 years ago

Tracking the failures in https://github.com/dotnet/arcade/issues/8766. Gonna close this issue in the meantime since we have validated that issues are being opened, at least.