Deployment Matrix

As you run more environments, it becomes hard to keep track of which version of each package is on which one. The Deployment Matrix lays it out as a grid — every package down the side, every environment across the top — so you can see at a glance what is deployed where, and where environments have fallen out of step.

The Deployment Matrix
The Deployment Matrix — deployed package versions per environment, with out-of-sync packages highlighted

Reading the matrix

Each row is a package and each column is an environment. A cell shows the version of that package currently deployed to that environment, or a dash when it is not installed there. When the same package sits at different versions across environments, the cell is highlighted — that package is out of sync.

The summary across the top counts the total packages, the package types in play (unlocked, source/data, managed, org-dependent), and how many packages are out of sync.

Where the next diff build starts

Baseline popover of a diff package on the Deployment Matrix: Next build starts from prod, with prod setting the build start and uat having no baseline
The baseline popover of a diff package: prod sets the build start and uat has no baseline

The Baseline column shows, for a diff package, the commit its next build starts from. Click it to see Next build starts from with the environment (or the default baseline) and the commit, and each environment's part in it: sets the build start for the environment whose baseline is furthest behind, counted, no baseline, inactive or unresolved. Hover over a label for what it means. The rule is described in How the baseline is resolved for a build.

Using it

Use the matrix to answer questions like "is staging behind production?", "did this package make it to UAT?", or "which environments still need this release?". Search by package name to focus on one, and click a version to see more about that deployment.

On this page