Skip to content

Pipelines Overview

Pipelines are the heart of FlightStack. They define your CI/CD workflow visually, specifying what to build, when to build it, and where to deploy.

A pipeline is a visual workflow consisting of:

  • Triggers - What starts the pipeline (push, tag, PR, schedule, manual)
  • Jobs - What actions to perform (build, test, deploy, notify)
  • Connections - The execution order and dependencies
┌──────────┐
│ On Push │ ← Trigger
└────┬─────┘
┌──────────┐
│Run Tests │ ← Job
└────┬─────┘
┌────┴────┐
│ │
▼ ▼
┌───────┐ ┌───────┐
│ iOS │ │Android│ ← Parallel Jobs
└───┬───┘ └───┬───┘
└────┬────┘
┌─────────┐
│ Notify │ ← Final Job
└─────────┘

Visual Editor

Drag-and-drop interface - no YAML required

Multiple Triggers

One pipeline can have multiple triggers

Parallel Execution

Run jobs in parallel for faster builds

Conditional Flow

Branch your pipeline based on conditions

TriggerDescriptionUse Case
ManualRun on demandProduction deploys
On PushCode pushed to branchCI builds
On TagGit tag createdRelease builds
On PRPull request opened/updatedPR validation
ScheduledCron scheduleNightly builds
  • CI Build - Full Flutter build for any platform
  • Build iOS - iOS-specific build (IPA)
  • Build Android - Android-specific build (APK/AAB)
  • Run Tests - Execute Flutter tests
  • Code Analysis - Run dart analyze
  • Deploy iOS - Upload to TestFlight/App Store
  • Deploy Android - Upload to Google Play
  • Deploy Web - Deploy to Firebase Hosting
  • Notification - Send Slack/Discord notifications
  • Shell Script - Run custom commands
  • Webhook - Call external APIs
  • Manual Approval - Pause for human approval
StateDescription
ActivePipeline is enabled and will trigger
DisabledPipeline won’t trigger automatically
DraftPipeline is being edited (unsaved changes)
  1. Open the FlightStack app
  2. Navigate to your repository
  3. Go to Pipelines tab
  4. Click Create Pipeline
  5. Drag a trigger onto the canvas
  6. Add jobs and connect them
  7. Configure each job
  8. Click Save