Skip to main content

Pipelines Overview

Learn how to create and manage CI/CD pipelines in Sluice.

Pipelines

Pipelines are the heart of Sluice. They define the complete workflow for building, testing, and deploying your applications.

Creating a Pipeline

To create a new pipeline:

  1. Navigate to Pipelines in your dashboard
  2. Click Create Pipeline
  3. Enter a name and optional description
  4. Click Create

Your pipeline starts with no stages. Use the visual editor to add and configure stages.

Pipeline Structure

A pipeline consists of:

  • Metadata: Name, description, and settings
  • Stages: Ordered list of steps to execute
  • Variables: Environment variables available to all stages
name: my-pipeline
description: Build and deploy my application
stages:
  - name: source
    type: source
    config:
      repository: https://github.com/org/repo
      branch: main
  - name: build
    type: build
    config:
      dockerfile: ./Dockerfile
      image: registry/my-app
  - name: deploy
    type: deploy
    config:
      type: kubernetes
      namespace: production

Pipeline States

Pipelines can be in several states:

StateDescription
DraftPipeline has been created but never run
ActivePipeline has been run at least once
DisabledPipeline is temporarily disabled
ArchivedPipeline is archived and read-only

Managing Pipelines

Editing

Click on a pipeline to open the editor. Changes are saved as new versions, so you can always roll back.

Versioning

Every save creates a new version. View version history in the Versions tab to:

  • See configuration changes over time
  • Compare versions side-by-side
  • Roll back to a previous version

Deleting

To delete a pipeline:

  1. Open the pipeline settings
  2. Scroll to the danger zone
  3. Click Delete Pipeline
  4. Confirm the deletion

Running Pipelines

Manual Runs

Click Run Pipeline to trigger a manual run. You can optionally:

  • Select a specific version to run
  • Override environment variables
  • Add a run description

Webhook Triggers

Configure webhooks to trigger runs automatically. See Webhooks for setup instructions.

Run History

View all runs in the Runs tab. Each run shows:

  • Trigger type (manual, webhook, scheduled)
  • Status and duration
  • Git commit information
  • Stage-by-stage breakdown

Next Steps