CircleCI

Hosted pipelines with docker, machine, macOS, Windows or self-hosted runner executors.

Provider
default
Category
Operations
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
approvalRequiredboolean—no—▸ false
artifactSigningboolean—no—inherited
concurrencyinteger—no—inherited
contexts · component propertyboolean—nofalseinherited
executorType · component propertyenumdocker | machine | macos | windows | self-hosted-runnernodockerinherited
jobType · component propertyenumbuild | approval | release | no-opnobuildinherited
managedboolean—nofalse▸ true
secretsFromVaultboolean—no—inherited
selfHostedRunnersboolean—no—▸ false
triggerenummanual | commit | pull-request | scheduleno—▸ commit
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "circleci", component: "circleci" }
Other CI/CD pipeline products · 56
Alibaba Cloud DevOps Flowalibaba-devops-flowalibabacloudci-pipelineAWS CodeBuildaws-codebuildawsci-pipelineAmazon CodeCatalystaws-codecatalystawsci-pipelineAWS CodeDeployaws-codedeployawsci-pipelineAWS CodePipelineaws-codepipelineawsci-pipelineEC2 Image Builderaws-ec2-image-builderawsci-pipelineAWS Protonaws-protonawsci-pipelineAWS Telco Network Builder (TNB)aws-tnbawsci-pipelineAzure Deployment Environmentsazure-deployment-environmentsazureci-pipelineManaged DevOps Poolsazure-managed-devops-poolsazureci-pipelineAzure Operator Service Managerazure-operator-service-managerazureci-pipelineAzure Pipelinesazure-pipelinesazureci-pipelineAzure VM Image Builderazure-vm-image-builderazureci-pipelineArgo CDargo-cdci-pipelineAtlantisatlantisci-pipelineAutomation pipelineautomation-pipelineci-pipelineAnsible AWXawxci-pipelineAtlassian Bamboobambooci-pipelineBuildkitebuildkiteci-pipelineChef Infrachefci-pipelineGeneric CI/CD pipelineci-pipelineci-pipelineConcourseconcourseci-pipelineCrossplanecrossplaneci-pipelineDeepEvaldeepevalci-pipelineDronedroneci-pipelineFluxfluxci-pipelineGitHub Actionsgithub-actionsci-pipelineGitLab CI/CDgitlab-cici-pipelineHCP Terraformhcp-terraformci-pipelineJenkinsjenkinsci-pipelinePipeCDpipecdci-pipelinepromptfoopromptfooci-pipelinePuppet Enterprisepuppetci-pipelineSalt Projectsaltci-pipelineSpinnakerspinnakerci-pipelineJetBrains TeamCityteamcityci-pipelineTektontektonci-pipelineTravis CItravis-cici-pipelineWoodpecker CIwoodpeckerci-pipelineZuulzuul-cici-pipeline
and 16 more → CI/CD pipeline page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# CircleCI: hosted pipelines configured in .circleci/config.yml. "Configuration reference" lists the
# job types "release, approval, no-op, build (default)", so a manual approval job is opt-in, and
# says "One executor type should be specified per job"; self-hosted runners are an added option.
schemaVersion: "1"
type: "component"
id: "circleci"
kind: "ci-pipeline"
provider: "default"
docs: "https://circleci.com/docs/reference/configuration-reference/"
defaults:
  trigger: "commit"
  approvalRequired: false
  selfHostedRunners: false
  managed: true
properties:
  executorType:
    type: "enum"
    values: ["docker", "machine", "macos", "windows", "self-hosted-runner"]
    default: "docker"
  jobType:
    type: "enum"
    values: ["build", "approval", "release", "no-op"]
    default: "build"
  contexts:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/circleci.md