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
Ability to specify which environment variables are masked by Secret Masking
In some cases environment variables are useful to print out, it would be helpful to be able to whitelist the ones we'd like to show. CCI-I-1223
Pre-populate parameter names in "Run Pipeline" feature
When using the "Run Pipeline" feature, the name of the parameter is currently left blank, and open to incorrect use. It would be useful to pre-populate this with a list of parameters that have been defined within the config file.
Additional field "description" on context variables
A human readable summary of the variable and its intention. This would be useful when the variable name is confusing or obfuscated to make sure intention of the variable is understood. Could include details for environment, team or notes on use. CCI-I-788
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
Ability to search for workflows
Right now in the UI you can easily search for all the workflows run for a project. However, there is no way to search for the jobs for a specific workflow. If I want to find a specific run of a job for a specific workflow there is no way to currently do this via the UI. The easiest way to achieve this in my opinion is to add another dropdown after the project one (seen below) for workflows. This way you can select the project/workflow you want.
Credit usage forecast using existing metrics in the UI
It would be great to have a one stop shop to view future forecasted credit usage based on current usage and data provided in the UI. This would help customers to better plan usage of features and resources instead of reacting to spikes in credits as they happen.
Allow branch whitelist to override “Only build pull requests”
This is mostly copied from a thread in the Community Forum here - https://discuss.circleci.com/t/allow-branch-whitelist-to-override-only-build-pull-requests/6392 The goal is to be able to have Circle automatically build all commits to the default branch as well as other specially named branches without having to build non-PR branches. This is very useful for those of us who have expensive steps in our build process (like tests that run on external servers, or those using the mac OS builds who want to save minutes). Minimum viable here would be to allow a list of branch names. Better would be to allow a list of branch names and/or regexes to specify branches. We have a work-around that we developed locally by opening up fake PRs from our release branches into master as part of our process. But it's manual, error prone, and inelegant. Supporting a whitelist would be much nicer. CCI-I-215