Overview

Salus pipelines are the backbone of the DevSecOps platform. They automate the software lifecycle from code integration to deployment, with security and quality checks built into every stage.

The pipeline dashboard gives you a centralized, real-time view of all the pipelines for a project, so you can track status, spot bottlenecks, and manage your workflows at a glance.

Every pipeline runs through five stages:

• Prepare
• Build
• Unit testing
• Package vulnerability scanning
• Deploy

For each pipeline run, the dashboard shows:

• Progress status — the real-time status of the run (see below).
• Duration — how long the run took from when it was triggered.
• Commit message — the change being built, from your Git provider.
• Triggered by — the member who started the run.
• Trigger time — when it was triggered.
• Trigger method — automatic (a push to a tracked branch) or manual (running the pipeline from Salus).
• Per-stage status — status of each stage in the run.
• Logs — jump to the run’s logs.
• Cancel — stop a run that’s still in progress.

Trigger methods

A pipeline run starts one of two ways:

• Automatic — Salus starts a run when your tracked source changes: a push to the tracked branch, or a new tag, depending on the deployment strategy chosen in the environment’s release configuration. This is the continuous-delivery default.
• Manual — you start a run yourself from Salus, building the current state of the tracked branch or tag. Use this to redeploy without a new commit, or when you want to control exactly when a release happens.

Each run’s Trigger method column shows which of the two started it, alongside who triggered it and when.

Pipeline stage summary

Hovering over a pipeline’s stages gives you a high-level summary of how each stage did, so you can decide whether to open the pipeline details for a closer look.

Pipeline statuses and what they mean

• Pending — queued, not started yet.
• Waiting — no task in the stage is running yet, but at least one is set to run.
• In progress — at least one task is running.
• Successful — passed with no warnings.
• Warning — completed, but with warnings.
• Failed — at least one task failed.
• Skipped — the stage was set to skip.
• Canceled — the run was canceled.

Troubleshooting

• The pipeline failed at a quality or security stage. Open the stage’s report in pipeline details to see what failed. If the stage is set as a gate in pipeline rules, the run stops there by design until the underlying issue is fixed.
• The pipeline succeeded but nothing deployed. Check the environment’s Automated Deployments setting — when it’s off, a successful build waits for you to deploy manually.
• You need to stop a run. Use Cancel on the run — it works while the run is still pending, waiting, or in progress.