A Razorops Pipeline is the name of the code repository for which it automates workflows, tests and deployments. You can find list of pipelines in the dashboard. Here is an example -

Sample Pipeline

You can optionally configure settings, secrets, and team members who may have access to a pipeline afterwards.

After a GIT repository on Github, Bitbucket or Gitlab is authorized and added as a pipeline, every code change triggers a build and automated tests in a clean container configured for your requirements.


A Workflow is a pipeline run triggered by a code change, webhook or API call. It's a set of rules for defining a collection of tasks and their execution order in a special file (.razorops.yaml). Workflows are implemented as a directed acyclic graph (DAG) of jobs for greatest flexibility. A workflow consists of multiple stages/tasks, each of which will be run in order. if a task fails, then the workflow is considered failed and the following tasks will not be started.

Sample Workflow


A task consists of multiple commands, each of which will be run in order. If a command in a task fails, then the task is considered failed, and unless specified otherwise, the rest of the commands in the task will not be run.

Sample Task


A workspace is a working directory shared by all workflow tasks. A workspace stores data unique to the task, which may be needed in downstream tasks. In the beginning of a pipeline, source code is checked out to the workspace. The command for every step bootstraps in the workspace. During a pipeline execution, the artifacts from a previous step will be available in future steps. The working directory is an ephemeral volume and will be cleaned out when a pipeline execution is finished.