Feature Requests

To run a certain set of tests, you need to utilized a "logged in" shell. Currently in the Linux VM, this is not possible. This feature request is to bring this functionality to the Linux executor.

Provide a mechanism to disable workflow/pipeline steps if certain conditions are not met, these should be enabled as soon as the conditions are met. Some use cases are: Disable Approval steps during Fridays or holidays Disable Approval steps for a certain user

Currently, you passing parameters to IP ranges is not supported. The following syntax is supported : circleci_ip_ranges: true This feature is in request of supporting the following syntax: circleci_ip_ranges: << parameters.true_or_false >>

Adding the ability to run restore_cache on a step failure would allow for saving time on potentially expensive post-failure actions. This could help with cleanup steps or aggregation steps.

Bug report can't access8

We are encountering a limitation where the compiled config exceeds the 8MB size limit, resulting in errors that prevent our CI/CD pipelines from running. To optimize the compiled config file, we propose removing all comments during the compilation process. By excluding comments, we can allocate more space for essential statements and commands, thereby enhancing the overall efficiency of our CI/CD pipelines. The underlying processes do not require comments, so this change would streamline the configuration without sacrificing functionality. Implementing this feature would significantly improve our workflow and reduce interruptions caused by the file size limitation. Thank you for considering this enhancement!

As title. Case 1: I have multiple setup steps to do before doing the actual thing. The setup steps doesn't depend on each other, each one takes some time to complete and all of the setup steps are not resource intensive. E.g. Package manager download dependencies and setup gcloud doesn't depend on each other, they can be done in parallel. Case 2: https://ideas.circleci.com/cloud-feature-requests/p/savecache-should-be-backgroundable If I can do steps in parallel, I can save a lot of time from waiting for workflow complete.

I'm using the VS Code extension, but I presume it's the language server (?) that would be responsible for this. I want to be able to add some kind of ignore next line/current line to suppress warnings and (possibly) errors, so it doesn't continue to report problems that I've address/am intentionally leaving.

Would like to have a feature to pass parameters to job running in current pipeline. We have trigger pipeline option where we can accept input from user but that triggers a new pipeline separately. There are situations where some input is to be accepted from user for a job and that will be used to run some command from job which works with version which is inputted . Will be happy to have this working. We have similar feature available with Gitlab pipelines with us. Attached image for reference we want this to achieve through config.yml and not through api or some other way Thanks, AkshataK

When using an orb owned by another org, it is not currently possible to add a when: on_fail to the command if it is needed. It would be helpful to always run certain commands from orbs.