CircleCI Ideas
Create
Log in
Sign up
Home
Feedback
Feature Requests
1919
Boards
Feature Requests
Server
Powered by Canny
Feature Requests
Tell us what you'd like to see added to CircleCI.
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
Complete
posts in
All Categories
All Categories
Config (82)
Monorepo (11)
Workflow Mgmt (114)
Build & Deploy (238)
Contexts (88)
VCS-Specific Asks (35)
Security (93)
UI & UX (441)
Plans & Pricing (40)
Legacy Functionality (8)
Other (300)
Dynamic Config (Set-up jobs) (7)
IP Ranges (open preview) (8)
Testing (71)
Roles & Permissions (7)
Caching (40)
Chunk/AI (1)
Enable Run From Failed Button before the Pipeline finishes (when the first task returns Failure)
0
1
Add Option To Select Checkout Depth and Path
Having an option in between a full checkout and a blobless checkout would be helpful for situations where comparing the previous commit or a single file is needed , but not the rest of the data.
0
3
Add rerun status metadata to job API
It would be helpful to know if a job was rerun by looking at the data provided via API
0
2
Configurable task timeout for runner
If a job run on container agent takes longer than 10 minutes to spin up, the pod is killed and the job fails. Allowing for a configurable task timeout would support jobs that take longer to spin up, reducing failures due to orchestration.
0
4
Ability To Set Max Build Runtime Greater Than 5 Hours
For jobs, such as machine learning or regression testing, a runtime greater than 5 hours can be required. Having the ability to set the max build runtime greater than 5 hours would be helpful for these use cases.
0
7
Associate Workflow With Deploy
Deploys only appear in the deploy dashboard when the deployment job or the job with the marker runs, meaning there is a delay between the trigger and the deployment appearing. The deploy also only provides the job's status and not the status of the workflow the job is contained in.
0
2
Add Option To Respect Image Defined In Container Runner Helm Chart
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.
1
2
Add support to only build on approved PRs
It would be great to have an additional option to only build on approved PRs. If there is an open PR on a non-default branch while "only build on PRs" is enabled, all commits to the branch will build which can be undesirable behavior.
1
3
Support triggering builds via comments on Pull Requests
Would be nice to be able to trigger certain builds or jobs by commenting on a pull request. CCI-I-1213
11
·
under review
68
Become a "Trusted Publisher" for NPM packages
Only GitHub Actions and GitLab are supported Trusted Publishers for NPM packages right now ( https://docs.npmjs.com/trusted-publishers#supported-cicd-providers ). With the rapidly upcoming changes to NPM ( https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/ ), CircleCI should become a Trusted Publisher.
2
4
Load More
→
Powered by Canny