CircleCI Ideas
 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit CCI-I-606 allow private namespaces for orbs w/ CircleCI.

Private Orb Registry Merged

As a company we often have parts of our build process that must remain private. It would be nice to be able to share configuration through orbs versus copying and pasting YAML from project to project however, we would not want this in the public registry. Is there or can their be support for hosting a private orb registry. If that is not available, offer private namespaces in the current registry?

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 16 2019
  • Taking votes
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    08 Feb 15:38

    https://circleci.com/ideas/?idea=CCI-I-606

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    05 Aug 19:11

    Perhaps this is a dup of https://ideas.circleci.com/ideas/CCI-I-606?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Sep 23:42

    Hi Everyone! It is now possible to unlist orbs from the registry search results by using our CLI. Documentation to do so can be found at: https://circleci-public.github.io/circleci-cli/circleci_orb_unlist.html.

     

    Please note that:

    • Unlisted orbs can be listed in the orb registry again with the same CLI command.
    • Only org admins can unlist/list orbs.
    • Unlisting an orb does not affect its ability to be referenced by name in builds or for its source to be viewed.
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Sep 23:47

    Thanks for the update! Are there any plans to develop fully privately orbs? This is a blocker for our use-case as well.