Generic CI/CD pipeline

CI/CD pipelineci-pipeline

Vendor-neutral CI/CD pipeline. Use when the real product is not in the catalogue; every rule for this kind still applies.

Provider
default
Category
Operations
Official docs
not recorded
Generic?
Vendor-neutral: the kind itself
Properties · 0 set by this component
propertytypevaluesrequireddefault
approvalRequiredboolean—no—
artifactSigningboolean—no—
concurrencyinteger—no—
managedboolean—nofalse
secretsFromVaultboolean—no—
selfHostedRunnersboolean—no—
triggerenummanual | commit | pull-request | scheduleno—
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: "ci-pipeline", component: "ci-pipeline" }
Other CI/CD pipeline products · 56and 16 more → CI/CD pipeline page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# The vendor-neutral CI/CD pipeline: the kind itself, with no product behind it. It sets no
# defaults and adds no properties, so every required kind property stays required on the node.
schemaVersion: "1"
type: "component"
id: "ci-pipeline"
kind: "ci-pipeline"
provider: "default"

The same page as markdown, for an agent: /catalogue/components/ci-pipeline.md