question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fix Race Condition between Queue Insights & AzDo Build Checks

See original GitHub issue
  • This issue is blocking
  • This issue is causing unreasonable pain

QueueInsights needs to obtains the list of pipelines from a given PR. Currently, this is done by using GetBuildCheckRunsAsync from IGitHubChecksService which parses the checks from Github for a given PR. However, we manage to beat AzDo in fetching these checks before they posted them.

There are two solutions for this that I can see:

  1. Add a new Controller in HelixAPI that listens to events from AzDo, and then post the queue insights check
  2. Wait a certain amount of time or loop untill we get all the build checks.

What are your thoughts? @ulisesh @ChadNedzlek @AlitzelMendez @riarenas

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
meloticcommented, Jul 13, 2022

Thanks for the feedback. Integrating this into build analysis is the way to go.

0reactions
ChadNedzlekcommented, Jul 13, 2022

It seems like just putting this functionality in build analysis is probably the route to go… we want to provide some insights into every check that’s running, about all the builds that are related to that PR… that’s exactly what build analysis is doing. Adding an extra “and also go generate the queue insights check too” method call in the AnalysisProcessor (which already has all the information needed and all the timing/retry stuff in place) seems reasonable to me? It doesn’t feel like this “isn’t build analysis” enough that it needs to be exiled to a different project, it just a slightly broader definition of analysis. 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

avoid Race condition between the azure continuous delivery
I am deploying DEV environment in two pipelines that contains (Deployment(10 mins) + tests run on deplyment (10mins) post deployment) for each ...
Read more >
Race condition in Azure Service Bus queue #43
I think the "correct" solution is to document that it's a dangerous method and shouldn't be used in multi-threaded environments. Once one part ......
Read more >
Troubleshoot pipeline runs - Azure DevOps
Learn how to troubleshoot pipeline runs in Azure Pipelines and Team ... Check the Override the YAML trigger from here setting for the...
Read more >
Azure Devops pipelines are remaining in queued status ...
Hi Team, I am exploring Azure DevOps as beginner. I have performed the steps as per given in Microsoft documentation ...
Read more >
Durable Orchestrations - Azure Functions
Introduction to the orchestration feature for Azure Durable Functions. ... However, race conditions are possible when orchestrations ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found