SHIP / Pipelines

Turn a change intoa repeatable release.

Build your workflow visually or edit its YAML. Run on your own machines, follow the logs, and keep the results beside the run.

Get started Read the pipeline guide

Pipeline run with passed stages and step logs — A recorded run, with stage status and the selected step’s output.View original capture ↗

BUILT FOR THE WORK

What you can do with Pipelines.

Two ways to work

Use the visual editor to organize stages or work directly in YAML with suggestions, hover help, and inline problems.

Choose the runner

Run in a fresh container on the Zelyq server or connect Linux, macOS, and Windows machines over SSH. Choose runners per stage when work needs different tools.

Build reusable workflows

Parallel stages, matrices, templates, plugins, caches, and service containers give recurring work a reusable structure.

Follow the result

Read live logs, collect artifacts and JUnit reports, and report status to GitHub or GitLab. Add approvals where the next step needs a person.

A CLEAR PATH THROUGH

From setup
to your next step.

Follow the guide for configuration details and the complete workflow.

Open the documentation

01Choose a source repository or app
02Define stages visually or in YAML
03Start manually, from Git, or on a schedule
04Review results and deploy through an environment

A SMALL EXAMPLE

A minimal test and deployment workflow

Create the referenced app and staging environment first. The pipeline file stays readable and reviewable.

release.yaml

name: Release
runs-on: local
source: { app: Shop }
stages:
  - name: Test
    steps:
      - checkout: true
      - setup: node@22
      - run: npm ci && npm test
  - name: Deploy
    steps:
      - deploy: { to: staging, port: 3000 }

ONE WORKFLOW / TWO VIEWS

Visual when you want the picture.
YAML when you want the details.

The visual editor showing the same Fieldnotes release pipeline — The visual editor · Fieldnotes release

The YAML editor showing the same Fieldnotes release pipeline — The YAML editor · Fieldnotes release

BEFORE YOU BEGIN

A few useful details.

Can I run a pipeline without using the AI app builder?+

Yes. A pipeline can source files from a Git repository as well as a Zelyq app. Start with the codebase you already have.

What can trigger a run?+

Manual runs, Git pushes, pull requests, schedules, upstream pipeline completion, app changes, and authorized external systems are supported. Configure the triggers you need.

Can every runner build Docker images?+

No. The default local container runner does not include Docker. Use an SSH runner with Docker available for Docker image build steps.

MAKE IT YOUR WORKSPACE

Start with the work in front of you.

Run Zelyq yourself and connect the parts your team needs.

Get started