Feature Requests

It would be great to have a metric available in the Insights that shows the time being spent by pipelines being on hold. I think customers will be interested to do analysis on such idle time which potentially could identify slow processes in the delivery pipeline and ultimately give the tools to improve speed

Currently the image defined in a container runner's helm chart will be overridden by the image defined in the job's configuration. In some cases it would be helpful to use the image defined the in helm chart, instead of having to a customizable service container.

Please add this option to run builds manually in a user friendly way. It's ClickOPs I know, but this is what we need to offer to developers sometimes, few clicks and 3 sec later your build is done and we are not a blocker anymore. https://circleci.com/docs/triggers-overview/#run-a-pipeline-from-the-circleci-web-app

As described in https://discuss.circleci.com/t/product-update-infrastructure-failure-badge-in-circleci-ui/47282/8 from the customer standpoint it is unclear why the server (especially when reliant on app.circleci.com ) has failed. We've tracked a few of these back to there being issues with memory but there are a few other causes such as using a port in the range of 32768 - 60999 ( https://circleci.com/docs/executor-intro/#port-ranges ) which support suggested may be a problem. As a customer troubleshooting build failures on a system that's been stopped by an outside event it's basic troubleshooting for us to have a reasonable error message to work with.

At the moment you can "opt-in" for specific branches, or view all branches on the Insights view. I'd like to be able to exclude particular branches (in this case actually just master ) as it has a different workflow (excludes some tests that are particularly slow). This would allow me to get more accurate metrics, as currently the runs against master are pulling down both the average and the p95 making it difficult to know how slow things really are.

It would be beneficial for user to simply use existing AppSpec.yml in their repo to deploy their ecs and update them.

CircleCI's lack of support for tags is really frustrating. This has frustrated me for a long time but today I've realised that there is no way to trigger a tagged build AND include pipeline params like you can for a branch. WHY?!? Please add support for this. Honestly, there's been some internal discussion about moving away from CircleCI and moving to GitHub Actions which I've always been opposed to but if we can't do simple things like trigger a pipeline with a parameter I think we're going to have to make the move. :-( And yes, I am aware that this can be achieved via an API call. In some ways this make it worse as your platform clearly supports the feature you just have not bothered to add it to the UI!

I have a requirement to trigger a pipeline using CircleCI's v2 API. It is not currently available on the Gitlab integration and the endpoint throws Http status code 500.

We're on a free account and, besides lots of stale branches, we're also running against storage limits but see no way to clear or manage this (other than clearing the DLC, which didn't help). I contacted support and they suggested changing retention periods or other settings which are not available for free plans. It would be ideal if we could clear storage by selecting specific branches, but if that's too much to ask, a simple "nuke" button to clear any and all stale branches, caches, or any other storage, would be great.

Add checks to the AWS ECR Orb to verify if components such as the AWS ECR Credential Helper are already installed so it can skip the process. They could also be set to be skipped so they can be installed as needed