Workflows in orbs
I want to be able to define an entire workflow in an orb, using the jobs of my orb and allowing parameters to conditionally choose which jobs to run and allow parameterization of branch and tag filters as well. CCI-I-615
Allow to use third-party orbs by white list
Currently "Allow Uncertified Orbs" of "Orb Security Settings" have binary option to allow to use third-party orbs or not.We wish to use WHITE LIST orb provider. CCI-I-687
Allow deleting Private Orbs
Allow the deletion of private orbs so users can stay within their orb limits. Private orbs have a limited scope of users, so if the owner is aware of the risks of breaking internal CI pipelines then they should have the option to delete orbs as necessary.
Allow non-Owners to publish Orbs (aka granular permissions for orb publishing)
Could be a project level API key with publishing permissions, or use team membership like contexts do. Some means to expand the population of folks who can deploy prod versions of orbs without giving them global admin rights in GH. CCI-I-1108
Allow Private Orbs along with Certified Public Orbs
We are on Scale Plan and when I try to create a private orb, it requires me to toggle on "Allow all members of my organization to publish dev orbs, use uncertified orbs and use third-party ..". in the organization settings. However, in our scenario, we only want to allow private orbs along with certified public orbs. Please add a third option apart from the existing binary options: Yes: Allow all members of my organization to publish dev orbs, use uncertified orbs and use third-party .. No: Only allow my organization to use orbs certified and supported by CircleCI
Extend Executors with images
We've started using custom orbs, these define a base image, say cimg/clojure:<tag>. We'd like to also offer executors with common tools, Localstack, MinIO, Redis, Postgres, etc. However there's no way of adding additional images to an executor currently. I'd suggest one of two solutions: Allow executors to have more images provided via parameters. Right now it isn't possible to have a when block in the executor config, or extend the executors Extend executor image config when specifying it, rather than replacing it. This would be a breaking change so it would likely need to be under a separate executor parameter, rather than docker Right now we're creating two executors, one with just the main runner for the core language, and another with Localstack and Minio, which is our common setup. If we ever need more docker images, we need to copy and paste that config from the orb for all the images.
Allow Sharing Of Private Orbs Across Separate Orgs
As a user who has projects spread across multiple organizations, it would be helpful if an org could be allowed to use a private orb from another org.
Allow list-type parameters in Orbs
It'd be useful to allow handling lists of values for a parameter, without having to resort to workarounds like parsing comma-separated lists in string types. I think it would be useful to be able to specify something like: steps: - myorb/foo: bar: - baz - qux And have the myorb/foo command called with a bar parameter equal to [ "baz", "qux" ] . CCI-I-701
Slack Orb: Only send a success message when a failed job is fixed but not on every successful build
I would like to use CircleCi's slack orb to get notified when a job fails and when that failed job is fixed. However, I do not want to receive a success message when all jobs build successfully. I only want to be notified if that particular job had failed in the past and is not fixed. CCI-I-1490
Slack notification on workflow fail/ pass event
Team, I did reach out to circle ci customer support for configuring slack notification on workflow fail/ pass. But after trying multiple solutions provided by Josh and team, we failed to achieve it. So please provide this feature. Requirement: Slack notification on workflow fail/ pass event Use case: Regression has multiple job setup to execute automation test cases in 5 containers. So once this jobs are completed I would like to receive a notification each job status in one line expected output: workflow master-regression failed Jobs: goals2019 - failed, rtf email_rtf- passed, profile- failed