Determining the number of queued jobs across the organization effectively

DevOps Azure DevOps
1

Hi, any suggestion on to determine how many jobs are queued over the entire organization?

2

At the org level check settings, then parallel jobs there is a screen there that will show you.

3

GitHub actions importer has an audit mode(?) that will scan an entire Azure DevOps org and will give you a neat report as well.

4

That screen is showing only the in-progress jobs

5

Ahh not just over time, but right now?

6

Not sure there is an org level commulative report. Per pool I suppose…

7

Wouldn’t be hard to script though

8

yes; I have a project pool that has the tendency to “occupy” all slots so I need to show upstairs what’s going on

9

There is a parallel over time report somewhere that will show you.

10

https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/pool-consumption-report?view=azure-devops|https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/pool-consumption-report?view=azure-devops

11

probably https://analytics.dev.azure.com/{org}/{project_id}/_odata/v4.0-preview/TaskAgentRequestSnapshots

12

And the GitHub actions importer will actually tally a report giving you the recommended number of runners to satisfy your Azure pipelines load, it might actually be quite useful

13

Its real late and I don’t have my work laptop fired up but I’ll see what I have laying around myself. I know I have a pile of agent pool/job/pipeline api calls in my postman collection.

I have that same trouble, complex pipelines from a single team project consuming an entire pool. There was a trend a while back where some pipeline engineers discovered they could run jobs/stages in parallel and I see runs that will consume 20+ agents at one time.