Pipelines

Pipelines are the execution of your CI/CD configuration. Each push, change request update, or scheduled trigger creates a new pipeline run.

How Pipelines Are Triggered

Pipelines are triggered automatically when changes are pushed to a repository. This includes direct pushes and merged change requests. The CI/CD system detects the push, reads your pipeline configuration, and starts a new pipeline run.

Viewing Pipelines

Navigate to your repository and click the Flows tab to see all pipeline runs. Each run shows its status, duration, and the commit that triggered it.

Pipeline Status

A pipeline can be in one of these states:

• Created — The pipeline has been created but not yet picked up.
• Pending — The pipeline is waiting for an available agent.
• Running — The pipeline is currently executing.
• Success — All steps completed successfully.
• Failure — One or more steps failed.
• Killed — The pipeline was cancelled.
• Error — The pipeline could not run because of a configuration or system problem.
• Skipped — The pipeline was skipped because a preceding step failed.
• Blocked — The pipeline is waiting for approval.
• Declined — The pipeline was blocked and declined.

Workflows and Steps

Each pipeline consists of one or more workflows, and each workflow contains one or more steps. Steps run sequentially within a workflow. Workflows may run in parallel if agent resources allow.

Viewing Logs

Click on a pipeline run, then click on a specific step to view its real-time log output. Logs include timestamps and are available for completed steps.

Cancelling Pipelines

You can cancel a running pipeline from the pipeline detail page. This stops all currently executing steps and marks the pipeline as killed.