Michael Yanni
Michael Yanni
@ocallesp I think the issue is determining exactly which commit of ours is in those builds. We're not synched enough on our schedule to have a 'release' build of our...
@drewnoakes Yeah, that's what I was thinking too. The main problem is having very old packages on NuGet that people are still downloading. 20+ downloads a day of those old...
Popping this back up for review.
Reviving this since I think it would be useful. See: https://docs.microsoft.com/en-us/azure/devops/boards/github/install-github-app?view=azure-devops
Consider investigating this as part of: https://github.com/dotnet/project-system/issues/7911
@tmeschter There is actually a mechanism that exists in Azure DevOps for this and only works on GitHub repositories (just our luck!): https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#comment-triggers Basically, it is that `/azp run` comment...
Will update this issue once PRs are created and then merged. Edit: Issue has been updated.
All required tasks are now completed.
@drewnoakes Looks like the `BuildUpdate_InvokesCommandLineHandlerWhenChangesExist` test is still failing for these changes.
@SeanFeldman I tried to send 50k messages in a batch for a stress test for the C# SDK (Track 2). I progressively reduced the number of messages until I found...