When a user commits/merges to a repository, CCI should run the step command and output should push to the same repository

The new performance plan eliminates queueing and provides flexible resource allocation, but customers often want to throttle or limit particular project's share in the overall resource pool.This is to request project based credit limits or quotas that would block or shape requests from specific projects if they go over a defined limit. CCI-I-624

Adding a flag to add to a config.yml file to enable SSH when a build runs. This eliminates the requirement to manually “re-run with SSH”. I don’t know about other people’s environments but certainly in ours, we know that a build is going to fail at least the first few times when we create it. Things that have been overlooked or parameters which have been missed cause the first few runs to be thwart with problems. Or, when you are troubleshooting a build issue and you expect the build to fail while you are adding erroneous test data etc. Rather than having to manually rerun the build again, especially after we already anticipate a build to fail would eliminate the need to wait for the build to run again, and potentially get stuck in a build queue for a second time for no reason. CCI-I-1149

Adding session tags or allowing for them to be added would allow for consolidation of roles. Currently a role needs to be created per project in some situations. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html#id_session-tags_adding-assume-role-idp

Hi there, How can I Skip one out of multiple Jobs, I understand there is [ci skip] but this will skip the entire jobs. I want a situation where I can only skip TEST out of Compile, TEST, BUILD jobs. Is this possible, if yes How?

The requires tag in workflows really limits what is possible. Requires makes a lot of sense for the deployment scenario used to demo it, but waiting for a group of jobs to complete (pass or fail) should be an option. Scenario: Setup -> Run multiple sets of tests in parallel -> Combine test results/coverage results/artifacts and report to PR That scenario above isn’t possible because if a single test fails in any of the jobs running in parallel the the fan-in step won’t run. CCI-I-344

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.

Some customers that are building for multiple architectures would like the ability to build both AMD and ARM images on Docker executors.

When a workflow is cancelled in CircleCI, it shows the running icon in BitBucket. This causes confusion, since it looks like builds are running for a long period. It would be very useful when a workflow is cancelled in CircleCI, it shows the same gray cancelled icon in BitBucket.

To reduce data transfer, it would be nice to specify a region to run all builds from. We only deploy to us-east-1 so running everything in that region would speed up ECR pushes and pulls. I'm guessing this would help with docker_layer_caching as well. CCI-I-241