Display Concurrent Job Usage | Feature Requests

Display Concurrent Job Usage

Colin

Desired State: users of CircleCI are able to identify how many jobs are currently running.
Current State: users of CircleCI are not able to identify how many jobs are currently running and must email an account manager for this information.
Impact: this prevents users from easily identifying the time period when jobs are being queued and prevents paid users from being able to verify if their jobs should be queued.

December 28, 2023

Henna Abbas

Merged in a post:

Running builds/jobs/containers view

Ville lahdenvuo Lahdenvuo

Currently there is no way to see the currently running operations except opening the "JOBS" page and scanning the list, however this does not show parallel jobs. It would be nice to see the currently running jobs/containers at the top of the page for example so you don't have to scroll and search for them.
For example we had a job that was stuck for 10+ hours and it was already gone from the first pages so we had to check multiple pages to find it and  terminate it. (This does not happen often, but still a good reason to be able to see running containers at a glance.)
CCI-I-810

4 days ago

Paul Pitt

This would be very useful. We spend quite some time investigating a pipeline issue, and it turned out to be concurrency. Without knowing, its kind of like flying blind.

Danny Allison

@ wacky flip This is an important visibility gap. Users should be able to see how many jobs are currently running in real time without contacting support. Providing this information in the dashboard or via API would improve transparency, help diagnose queue delays, and allow paid customers to better understand resource usage and limits.

Raphaelpr01@gmail.com

Yes, please! It's very hard to investigate concurrency issues without this information.

Giovanni Toledo

Please, implement this! We are hitting the limits and it is very hard to troubleshoot.

Jacob Myers

Yes please! We are hitting our concurrency limits, and it would be nice to be able to plot out on a graph the concurrency trends in order to help with mitigation and improvement

Ryan shillington

This "Legacy" view is pretty helpful. Unfortunately you can't kill the job (or re-run an old one) from it. https://app.circleci.com/pipelines/github/<YOUR_ORG>/<YOUR_PROJECT>/jobs

Garroway

Same problem here. Would be great to be able to filter the pipeline's page by 'Running'

Lito.kusnadi@carsguide.com.au

I'm having the same problem. Running out of containers to run job, and the only way to find out is to have an overall view of the jobs. Turns out 1 pipeline uses multiple containers to run in parallel. Also, I need to kill job from time to time and need ability to judge the least important job to kill. Going into each project one by one is not feasible.

Rafael Turk

We had a job stuck for 17+ hours beyond the first page

→