Share your feedback...
Support automatic retry of failed builds
It would be great if CircleCI allowed you to configure an automatic retry of a build upon failure. Ideally, you would be able to specify the max number of times you would like it to retry. Taken from: https://discuss.circleci.com/t/support-auto-retrying-of-failed-builds/13332/6 CCI-I-935
Allow multiple login sessions
Users need to be able to have multiple active login sessions because they often have to use CircleCI on both desktop and mobile devices. I often find myself having to login on my phone in order to re-trigger failed builds (sometime from flaky tests, and more frequently from random CircleCI timeouts). This apparently logs me out of my desktop session. Given that the unauthorized page doesn't provide users with a login link or redirect back to the desired page after logging in ( https://circleci.canny.io/cloud-feature-requests/p/redirect-to-login-page-when-viewing-pages-while-unauthenticated ), managing CI from multiple devices is a very frustrating experience. Neither of these should be issues in an age where people have to manage issues on their computer at work and during off hours on their phone. The initial response I received from support claimed that the single session is done intentionally for security purposes, but plenty of other secure applications allow for multiple sessions without incident.
Add option to Jobs to automatically Timestamp build logs with elapsed time or UTC
While CCI allows you to separate builds into steps, it's very common to find that a singular step is multi-phased itself. It would be extremely helpful if, within a build step, the output was timestamped. This is the Jenkins equivalent: https://wiki.jenkins.io/display/JENKINS/Timestamper I'd be most interested in the duration feature, more so that having the timestamps and needing to work out duration of steps myself. CCI-I-360
Allow users to add bots to an allowlist to avoid being blocked as an unregistered user
This feature request is to create an allowlist for users to add automated code updating tools and bot users (such as dependabot) to work while utilizing the Prevent unregistered user spend toggle.
Docker Layer Caching for multi-stage docker build
This is a request to implement Docker Layer Caching for multi-stage Docker builds which isn't currently supported.
Option to allow failures in Fan-In/Out Workflow
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
Redirect to login page when viewing pages while unauthenticated
If you visit a URL that requires authentication but are not authenticated, Circle shows a 404 error page. This is confusing (particularly in an enterprise installation) because it is not obvious that you need to log in and people may think that the link they followed is incorrect. Circle should redirect to the login page and then return to the target page after authentication, showing an error only if the page actually does not exist or the user does not have permission. CCI-I-459
Conditional manual approval steps in workflows
When running jobs, you might want to sometimes skip the manual approva for example when running an acceptance test - if everything is 100% then we can skip manual approval if things are less than 100% then we want to manually approve CCI-I-605
Allow restricted contexts within Bot account
This is almost the same request as the following post, but the Github bot needs access to Restricted Contexts as well. https://circleci.canny.io/cloud-feature-requests/p/allow-restricted-contexts-within-scheduled-workflows
Allow CLI to run machine jobs locally
At the moment we note that you can't run machine jobs locally: https://circleci.com/docs/2.0/local-cli/#limitations-of-running-jobs-locally However there are situations where jobs with a machine executor would be best tested locally, so adding support to the CLI would be great.