Event triggered Ci/CD with

Pipelines

It wouldn’t be a developer workflow without a CI/CD pipeline that you could use to customize your builds with.

A pipeline is a simple container that you can customize via your workflow YML and trigger from a workflow event or even trigger manually if you wish via Slack or the CLI.

Get Started

Learn more about

Pipelines

Pipelines are the corner stone of a good CI/CD workflow. They can be manually triggered from our CLI, Website or Slack but you can also connect them with workflow events to automate them as well.
Docker builds

Trigger docker builds from a Github merge request event and push images to any registry.

Static Sites

Easily compile a build of your static site and deploy the final code artifact to any hosting provider.

GitOps

Clone a repository, make some changes to your infra and check the code back in to version it.

Let’s show you the most basic

Example of Pipelines

Pipelines should be very familar for anyone who’s used a typical CI/CD server. They are a simple YAML definition that let’s you run code which can build, test and push your code artifacts.
STEP 1
ops.yml

Define your pipeline using YAML in your workflows code repository.

STEP 2
Build & Publish

Build your container and publish it to your team’s private registry.

STEP 3
Run or Trigger

Run your pipeline or trigger it from your Github via workflow events.

Pipelines fit perfectly into a

Platform as a Service

Pipelines can be used in a standalone manner, but they are more powerful when used with Commands, Services & Insights to help you build the perfect internal developer PaaS.

if you want to know more

Explore our Documentation

Overview

Read now

Get Started

Read now

Your expert questions answered by experts

Our team is here to help you get started or answer any questions you may have.