Pipeline commands

The pipeline commands manage your pipelines — the CI/CD definitions that build your code and deploy it to your cloud. They also expose build history and a combined timeline of every build and deployment in a project.

All pipeline commands need a project id. Pass --project <id> or set MICROTICA_PROJECT_ID.

List and inspect

pipeline list

List the pipelines in a project.

microtica pipeline list
microtica pipeline list --type template

By default the response drops those large fields to keep it small — they can run to hundreds of kilobytes per pipeline. Use pipeline get to fetch one pipeline with everything inline.

pipeline get

Show one pipeline in full.

microtica pipeline get <pipelineId>

Create and update

pipeline create

Create a pipeline that builds from a Git repository. Find the Git account id and repository URL with the git commands.

microtica pipeline create \
  --name my-app \
  --account <gitAccountId> \
  --repo https://github.com/acme/my-app \
  --branch-filter "^(main|develop)$" \
  --automated-trigger \
  --var NODE_ENV=production

pipeline update

Update a pipeline from a JSON body file (a raw UpdatePipelineRequest — all fields optional).

microtica pipeline update <pipelineId> --from-file ./pipeline.json

pipeline spec update

Replace just the inline microtica.yaml for a pipeline.

microtica pipeline spec update <pipelineId> --spec-file ./microtica.yaml

See pipeline syntax for how to write the spec.

pipeline delete

microtica pipeline delete <pipelineId>

Trigger a build

pipeline trigger

Manually start a build on a given ref. --ref is required and has no default. A plain branch name is normalized to refs/heads/<name>; you can also pass refs/heads/<name> or refs/tags/<name>.

microtica pipeline trigger <pipelineId> --ref main

# Override variables for this build only
microtica pipeline trigger <pipelineId> --ref main --var NODE_ENV=staging

The response includes the new buildId, which you can feed to logs build to watch it run:

BUILD_ID=$(microtica pipeline trigger <pipelineId> --ref main --query buildId | jq -r .)
microtica logs build <pipelineId> "$BUILD_ID" --follow

History

pipeline history

Return a project-wide, correlated timeline of builds and deployments — one row per logical run. This is the command to reach for most "what happened" questions; it accepts rich filters.

# Everything in one environment in the last 24 hours
microtica pipeline history --env prod --from "$(date -u -v-1d +%Y-%m-%dT%H:%M:%SZ)"

# Failed deploys only
microtica pipeline history --type deploy \
  --query "pipelines[?status!='SUCCEEDED'].{id: id, status: status, env: envId}"

Builds

For the raw build log of one pipeline, use builds. For deploy-history questions, prefer pipeline history or app last-deploy — they correlate the data for you.

pipeline builds list

List the builds of one pipeline.

microtica pipeline builds list <pipelineId>

Like pipeline list, this strips heavy per-build fields by default; pass --full to keep them, along with --offset and --limit to paginate.

pipeline builds get

Fetch one build with its steps, stages, metadata, and spec inline.

microtica pipeline builds get <pipelineId> <buildId>

--start-date <ms> narrows the lookup when needed.

Next steps

• Stream a build's logs
• Write a pipeline spec
• Connect a Git account