GitLab CI compiler

The gitlab target compiles a Sverka Definition Graph (from @sverka/workflow) into a GitLab CI pipeline — executable steps become jobs, needs: edges come from declared dependencies, and stages are derived from topological order. Special step kinds lower differently: component steps become include: entries, pipeline-call steps are inlined as namespaced jobs, and child-pipeline steps become trigger jobs.

Only the first root pipeline is emitted — a single .gitlab-ci.yml cannot express multiple pipelines, so additional roots are dropped.

CLI usageCopy Anchor Link

# Print YAML to stdout
sverka compile --target gitlab

# Write pipeline files into a directory
sverka compile --target gitlab --output-dir out/

Generated pipeline shapeCopy Anchor Link

Each ShellStep becomes a job with its command in script:; dependency wiring lands in needs:. Stages are computed by topological level — the first level is build, each later level is stage-N:

stages: [build, stage-1]
build:
  stage: build
  script:
    - bun run build
typecheck:
  stage: stage-1
  needs: [build]
  script:
    - bun run typecheck

Triggers come from the pipeline's Entry definitions; step rules map to GitLab rules: (if/when). Declared step secrets map to CI/CD variables.

Public APICopy Anchor Link

import { GitlabTarget, compileGitlab } from "@sverka/compiler";

const result = compileGitlab(graph);
// result.artifacts    — GeneratedArtifact[] (.gitlab-ci.yml)
// result.diagnostics  — capability findings

GitlabTarget implements the Target contract: analyze, lower, emit, compile.

Support levelsCopy Anchor Link

GitLab capability manifestCopy Anchor Link