Orbs in CircleCI Server
Within our company, we are trying to migrate 100+ repositories to use CircleCI. In each repository, the config.yml is very similar, with only a few parameters different. Orbs would be greatly simplify our migration process, as it would remove duplication as well as enabling bugs to be fixed in a single place. CCI-I-960
Build an orb for integrating with Artifactory XRay
Allow Whitelist for 3rd party Orbs
There is currently a control to allow or disallow 3rd party orbs. While this is ok, I would like the granularity control to introduce cleared and reviewed Orbs to my repo population to avoid unintentional introductions, vulnerabilities or issues. CCI-I-1161
It would be great if you could "install" an orb on an organisation level.This way you can specify some default values for the orb, fx. api-key/url etc. without having to specify that each time you want to use the orb. CCI-I-1497
Allow rebuild/rerun after orb expiration
Problem: When a CircleCI "build" fails because the orb version has expired you cant re-run this commit. If I publish the missing orb version, this commit is lost - even though this commit is actually just find and there's no change needed to the config. I must generate a new commit to get the changes to run. Solution: Allow me to rerun because I manually published the orb's alpha version.
Centrally managed configuration templates
We're encountering more use cases where customers want centrally managed configurations that can be called and used. For example, many projects may follow the exact same workflows, and any updates to a process need to be reflected in all projects. Orbs are a step in the right direction, but each project must still manually update the orb version to see new changes - a centralized change does not propagate automatically. Maybe if we added a "latest" tag for orbs? We also don't yet support templatizing workflows in orbs, so we still have to write a lot of config. Related ideas: https://ideas.circleci.com/orbs/p/workflows-in-orbs
Jira Integration - "Releases"
Please rename the heading "Releases" to "Deployments" within Jira. We are trying the CircleCI JIRA integration. It is showing CircleCI Deployment data within an individual JIRA ticket, on the right hand side of the JIRA Ticket. This information is shown under the title "Releases", but I think it should be "Deployments", as per DevOps convention. These may be Deployments to non-production environments, and doesn't account for when we use Feature Flag tools to Release software. Also, when you actually click on the Releases info, it brings you to a menu titled "Deployments"!
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 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
Mark skipped job with gray icon
I have a few workflows where we evaluate a branch for changed paths and do a circleci step halt if there are no hits. This works well enough, but the issue is that in the UI the job containing step is still marked in green (as is the skipped job). Ideally we would have a halt syntax that allowed recording a success, failure, or new (as far as I can tell) "skipped" state for the jobs that didn't run for a particular invocation (e.g. a PR changeset). CCI-I-1496