Spring Pipeline

Build, artifact and deployment state across Realm of Salt projects.

BUILD HEALTH

Pipeline activity

14-day overview

Visible build results across the selected period.

Passed Warning Failed Cancelled

Sort

Made with ❤ and 🍪

Legal Notice | Privacy Policy

PIPELINE ACCESS

Sign in

Private projects and pipeline actions are shown after sign in.

Username Password

PIPELINE CHECKOUT

Check for updates

Check the tracked remote branch first. Spring Pipeline only changes the checkout after you explicitly choose to update it.

Checking remote Looking for repository changes…

Pipeline checkout —

Remote —

Branch

Code update If an update is available, Update checkout fetches the selected branch, resets the Pipeline checkout to it, cleans generated files and stores the branch. It does not start a build.

PIPELINE

Run pipeline

Build an isolated copy without changing the normal Pipeline checkout.

Source

Local testBuild the current Pipeline checkout. Private to admins and never promoted to public releases. Live / repository branchBuild a selected GitLab branch. Visibility follows the project access policy.

Branch

Release stage

DevelopmentInternal moving build for active testing. Not intended as an official release. BetaShareable pre-release artifact. Can later be promoted to Stable without rebuilding. StableOfficial release stage. Use when this exact build is already release-ready.

Website target

DemoDefault: publish this exact artifact to Demo, check it, then promote it to Production without rebuilding. ProductionPublish to Demo and Production in one run, skipping the Demo check. Asks for confirmation.

Release artifacts Artifacts are archived in Spring Pipeline. Deployment stays separate.

BULK BUILD

Retry failed pipelines

Failed projects will be queued one at a time.

Serial queue Spring Pipeline still runs only one build at a time. Projects already queued or running are skipped. Repository/setup failures will fail again until their files are fixed.