Pipeline Forge
Documentation

How to build yourfirst pipeline

A step-by-step walkthrough of Pipeline Studio — from presets to generated YAML. Most teams are live in under a minute.

Open Pipeline StudioBack to home
Jump to step-by-step guide

What you get

Pipeline Forge covers the full path from commit to deploy.

Instant generation

YAML in seconds, not hours

Best practices

Security and quality built in

5 CI providers

GitHub, GitLab, Jenkins & more

Clean output

Production-ready formatting

Save & export

Local storage + JSON export

Fully customizable

Every pipeline knob exposed

Step-by-step guide

Follow in order, or jump via the sidebar on desktop.

8 steps
  1. 1
    Step 1

    Choose a quick preset

    Start from a template: Basic Node.js, Production Node.js, Python API, Docker/K8s, or Full Featured. Each preset applies sensible defaults you can tweak.

    Pro tips

    • Basic Node.js — simple apps with tests and lint
    • Production Node.js — security scans + deployment
    • Docker/K8s — container builds and orchestration
  2. 2
    Step 2

    Configure project details

    Set the project name, stack (Node.js, Python, Java, Go, Rust, .NET), package manager, working directory, and monorepo tool when applicable.

    Pro tips

    • Project name is used in generated file paths
    • Package manager drives install commands
    • Supports Nx, Turborepo, Lerna, and Rush
  3. 3
    Step 3

    Select your CI provider

    Pick GitHub Actions, GitLab CI, Jenkins, CircleCI, or Azure Pipelines. Tune concurrency, job timeout, retries, and parallel execution.

    Pro tips

    • GitHub Actions for repos on GitHub
    • GitLab CI for native GitLab integration
    • Jenkins when you need self-hosted control
  4. 4
    Step 4

    Configure pipeline steps

    Enable linting, unit tests, E2E tests, formatting, type checks, builds, security scans, dependency audits, Docker builds, and container scanning.

    Pro tips

    • Always run tests before deploy targets
    • Security + audit steps catch CVEs early
    • Docker when you ship containers
  5. 5
    Step 5

    Choose deployment target

    Deploy to AWS, Kubernetes, Vercel, Netlify, Heroku, Azure, GCP, Fly.io, Railway, Cloudflare Pages, or DigitalOcean — or skip deployment.

    Pro tips

    • Vercel / Netlify for front-end apps
    • Kubernetes for multi-service stacks
    • AWS ECS for container workloads
  6. 6
    Step 6

    Advanced features (optional)

    Add env vars, custom scripts, Slack/email notifications, matrix builds, artifacts, cron schedules, quality gates, performance tests, and service containers.

    Pro tips

    • Matrix builds test Node 18 / 20 / 22 in parallel
    • Notifications alert the team on failure
    • Schedules for nightly or weekly runs
  7. 7
    Step 7

    Save your configuration

    Name and store configs in browser local storage. Export JSON to share with teammates or version in git.

    Pro tips

    • Use names like prod-nodejs or staging-api
    • Export JSON before big refactors
    • Import JSON to restore a teammate's setup
  8. 8
    Step 8

    Generate and export

    Click Generate Pipeline, review syntax-highlighted YAML in the live preview, then copy or download. File names match your provider automatically.

    Pro tips

    • Copy for quick paste into your repo
    • Download commits as .github/workflows/ci.yml etc.
    • Re-generate anytime after config changes

Ready to generate your pipeline?

Open Pipeline Studio, pick a preset, and export YAML in one session.

Go to generator