Pipeline Guide

User and Developer Guide

Learn how Custy turns public profile names into ordered, reviewable Git and release workflows.

Commandcusty run

Quick Command

custy run PROFILE [PROFILE ...] [OPTIONS]

execution modelpublic profilesextension guide

Public Profiles

Execution

Sequential

Failure Policy

Stop and re-raise

Primary Entry Point

custy run

Overview

A Custy pipeline is an ordered collection of registered steps. A public profile such as dev or release selects a prepared collection; Custy resolves it, builds each step, and executes the result one step at a time.

This section explains the system behind the command. Use the Run command guide when you need syntax, options, examples, and troubleshooting for the CLI itself.

Explore by Goal

Pipeline Documentation

Run a Known Profile

Compare the six supported names and choose the smallest flow in Profiles.

Reference Every Profile

Find all 20 public, direct-command, nested, and aggregate definitions in the Complete Profile Reference.

Understand Priority

See all 28 priority entries and merged-profile sorting rules in Step Priority and Ordering.

Understand Execution

Follow resolution, registration, building, shared context, and failure behavior in Execution Model.

Combine Profiles

Learn deduplication and global ordering in Custom Composition.

Review Daily Development

See exactly what Dev includes and deliberately omits in Development Pipeline.

Review a Release

Trace validation through push in Release Pipeline.

Extend Custy

Understand the internal step contract, registry, builder, and test expectations in Step System.

Public Boundary

The current typed custy run argument accepts only commit, tag, push, dev, release, and full. Internal resolver profiles are used by Custy's implementation and direct commands, but they are not additional public Run names.

Public profile examples

bash

# Preview a daily development pipeline
custy --dry-run run dev

# Run a complete release pipeline

custy run release

# Merge two supported profiles

custy --dry-run run commit push

Important Safety Boundary

Pipeline execution is sequential, not transactional. If a step fails, Custy stops and reports the failed step, but it does not automatically undo changes made by earlier steps. Always inspect files, Git history, tags, and remote state before retrying.

Continue

Related Commands

Commands commonly used together with this command.

Execution Model

Follow a profile from CLI input to sequential execution.

Profiles

Compare outcomes, side effects, and recommended uses.

Complete Profile Reference

Inspect all 20 resolver profiles and exact expanded sequences.

Step Priority and Ordering

Review every priority and the merged-profile algorithm.

Pipeline Architecture

Trace profiles through resolution, registration, construction, shared context, and execution.

Run Command

Use the public command syntax, options, examples, and troubleshooting.

Overview​

Overview