Feature Requests

Currently, email notifications can be configured for either "All Builds in My Projects", "My Branches" or "None". It would be very useful to have an option to receive email notifications only for builds I'm the author of, i.e. "My Commits" rather than "My Branches".

CircleCI Terraform provider would be great addition as it would allow to manage CircleCI projects using code. CCI-I-374

We have a ton of projects which use CircleCI and one bad actor can easily use up our concurrency limit and cause queuing across our entire org. It would be great if we could configure per-project specific concurrency limits so we can have finer grain control and limit the impact any one project could have on others.

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

When setting the filter branches on the insights page this should extent to the flaky tests below. Currently, all flaky tests are shown regardless of the filtered branch. Showing only flaky tests from the filtered branched is not configurable currently. This makes it hard to differentiate between real/persistent flaky tests vs failed tests introduced by a momentary mistake. A flag to see it to all branches would be ok, but it can cause confusion when looking for flaky tests on a specific branch.

Currently Ubuntu machine images do not provide a user session, this negates the ability to access services such as: org.freedesktop.hostname1. org.freedesktop.Accounts, org.freedesktop.login1 org.freedesktop.secrets A full graphical environment would allow testing that involves desktop services such as Gnome keyring.

Our organisation has an issue of one repo taking 95% of Circle containers at any given time of any given day. They have extremely long build and test times and they seem to push every single commit. This gets in the way of other teams. It would be good to be able to put limits on the number of containers a single repo can use of our organisation's allowance. A good way for this to be handled would be once they hit their allowance their builds are always lower priority than other repos. CCI-I-292

I want to be able to see when the runner last ran a job and what job that was so I can see if the runner is still being used.

We are having problems getting all projects under an organization since we are using API v2. API v1 allowed us to obtain this information by requesting the organization's projects or getting info from "/me". With API v2, this is not possible, and we cannot find a way to get all projects of our organization to operate with them. How can we solve this issue? It would be helpful to have a "/projects" query to obtain this information.

RISC-V is an open standard instruction set architecture (ISA) that is gaining significant traction in the tech industry. As more companies and developers adopt RISC-V for various projects, from embedded systems to data centers, there is an increasing need for CI/CD tools to support this architecture.