Feature Requests

When a project is configured to use OIDC, it should be possible to use these credentials to pull a privates image(s) from GCR when starting the executor. Users currently have to pass in a long-lived service account key (image attached). OIDC can be setup for GCP (1), but private image pulls are not yet supported. (1) https://circleci.com/docs/openid-connect-tokens/#google-cloud-platform

Filters should allow for tags with branches not one or the other. It seems a pretty common use case to want only a branch to build but not run a deploy workflow unless branch:v1.0 tag has been added/approved/merged etc. CCI-I-305

As per https://github.com/circleci/circleci-docs/issues/2040#issuecomment-368139737 It would be nice for users to have a way to shallow clone. Currently, we do checkout to checkout. It would be nice to be able to pass a depth into that like shallowClone:10 and then use the number 10 as the depth for the clone. The PR linked has a modified version of the existing script that works. CCI-I-254

The old UI used to allow a view of the build queue. This was very useful as allowed one to see what was blocking the queue and contact the responsible teams. Without this screen there's no information about what's happening.

Provide automation for blue/green releases. Validation of a release would be based on a set of one or more user specified SLOs The failure to meet any one of the defined SLOs would cause the release to be immediately rolled back Rollbacks could trigger a CCI pipeline and/or call a user specified webhook or webhooks

CF has an out of the box ArgoCD integration that makes things like Canary deploys to k8s very simple. https://codefresh.io/docs/docs/integrations/argo-cd/

When viewing a job that had a large number of test failures (177 in my case) the CircleCI dashboard starts getting really bad performance. Every interaction with the page feels slower, like the browser is struggling to render it or something. The failures are being reported to Circle via jest-junit