Pipelines
Promote each change through every stage to Production.
A pipeline takes a git repository as the source and your environments as the stages. Each promotion validates against the stage, waits for approval where it is required, merges and deploys, and records what is deployed where.
One pipeline of two stages on Solo. Any number of pipelines on Team and above.
Stages that match your environments
Each stage pairs an environment with the branch that holds what it should contain, for example integration, QA, UAT and Production.
- 2 to 20 stages, each with its own test level and minimum test coverage.
- A board with the open pull requests and the changes waiting in each stage.
- One promotion into a stage at a time; others wait in its queue.
- Changes made outside the pipeline are found before they are overwritten.
Approvals, freezes and release windows
- 1 to 3 approvals per stage, from any approver or from named roles and members (Team and above).
- A member cannot approve their own promotion unless the Owner allows it.
- Freezes for every stage or one stage, with overrides granted by a permission.
- Release windows: outside them, a promotion is scheduled for the next window.
- Approval requests in Slack and Microsoft Teams, through webhooks.
Automation from your repository
- Validate pull requests: each new pull request is validated against the stage and the result is posted to it.
- Deploy when merged: a merge into the stage branch deploys it.
- Promote to the next stage when ready, up to the stage before Production.
- Repository events come from GitHub; other providers promote from the board.
Hotfixes and the steps around a deployment
- Hotfixes go straight into the last stage when the pipeline allows them.
- Bring back carries a hotfix into the stages it skipped (Team and above).
- Manual steps before or after a deployment, and automated steps that activate a flow or run an Apex script.
- Merge conflicts are resolved in a merge view.
Step-by-step help: Create a pipeline, Promote changes,Approve a promotion, Freezes and release windows.
Questions about pipelines
How does a Metacaliper pipeline work?
A pipeline has one git repository and 2 to 20 stages. Each stage pairs one environment with one branch. A promotion prepares a branch with the selected changes, validates them against the stage environment, waits for approval when the stage needs it, merges, and deploys.
Are deployments from a pipeline full or delta deployments?
A promotion deploys the components its changes touch, not the whole repository. When the validation ran tests and the branch has not moved, it deploys the validation with Salesforce quick deploy.
What happens to changes made directly in an environment?
Before it deploys, a promotion compares the components it changes with the environment. If some were changed outside the pipeline, the promotion waits until someone chooses to overwrite them or cancel, and a snapshot is taken before anything is overwritten.
Which plan includes pipelines?
Solo includes one pipeline of up to two stages. Team and above include any number of pipelines and stages, with approvals, pull request validation and bringing changes back to earlier stages.
Build your first pipeline
Start on Free to connect your environments and compare them. Pipelines start on Solo at $99 a month, with no per-user price.