CLI Pipeline Commands | FlightStack

Pipeline Commands

Two terminal-facing commands cover the pipeline lifecycle today:

• flightstack pipeline lint — validate pipeline / step YAML against the FlightStack spec.
• flightstack logs — read or tail logs for a pipeline run.

Authoring (drag-and-drop) and run history still happen primarily in the visual editor — see the Pipeline Editor.

flightstack pipeline lint

Run the FlightStack pipeline linter against a local YAML file. Catches structural issues (graph cycles, expression syntax, secret provenance, matrix sanity, malformed YAML) without hitting the server.

flightstack pipeline lint <file>

Options

Flag	Description
--json	Emit machine-readable JSON instead of the human renderer.
--strict	Exit non-zero on warnings as well as errors.

Examples

# Human-readable
flightstack pipeline lint .flightstack/pipeline.yml

# JSON for CI
flightstack pipeline lint .flightstack/pipeline.yml --json

# Strict mode for pre-commit hooks
flightstack pipeline lint .flightstack/pipeline.yml --strict

Sample output:

.flightstack/pipeline.yml:18:5  FS-W201  step 'voostack/deploy-ios@1.0.0' is not cached locally; resolution skipped
       hint: warning will not appear when running on the FlightStack runner

.flightstack/pipeline.yml:42:9  FS-E110  cyclic dependency: deploy-ios → build-ios → ci-build → deploy-ios

0 error(s), 1 warning(s)

Note

uses: references to marketplace steps are linted structurally but not resolved against the registry — the CLI runs offline. Unresolved refs become warnings unless --strict is set. For end-to-end validation, push your branch — the server-side linter resolves all refs.

Exit codes

Code	Meaning
0	No errors (and no warnings, if --strict).
1	Errors found, or warnings with --strict.
2	Bad invocation (missing file argument, file not found).

flightstack logs

Print logs for a pipeline run, optionally tailing as new output streams in.

flightstack logs <run-id>

Options

Flag	Alias	Description
--follow	-f	Tail logs — re-poll on --interval and print new entries.
--interval <seconds>		Poll interval when following. Default 5.

Examples

# Print the current log buffer once
flightstack logs 9c1f2d76-abcd-4321-9c0e-8a4ea7d1f5b2

# Tail with the default 5-second interval
flightstack logs 9c1f2d76-abcd-4321-9c0e-8a4ea7d1f5b2 --follow

# Tail with a faster cadence
flightstack logs 9c1f2d76-abcd-4321-9c0e-8a4ea7d1f5b2 -f --interval 2

Run IDs are visible in the visual editor under any pipeline run, and in the REST API under /pipeline/runs/{runId}.

Editing pipelines visually

The visual editor remains the primary way to compose pipelines. To open it:

1. Open the FlightStack app
2. Pick a repository
3. Go to Pipelines
4. Drag jobs onto the canvas, wire them together

The graph round-trips to YAML — what you export with the editor lints clean with the command above, and what you commit to your repo will load in the editor.

See Pipeline Editor for the full picture, or the Variables doc for how ${{ steps.X.outputs.Y }} flows between jobs.

Next steps

• CLI Repository commands to connect repos before authoring pipelines
• Pipeline Editor for visual authoring
• Variables & step outputs for wiring jobs together