Environments

The environment view lists the environments in whatever scope you browsed to, with the deployment that is live in each one. A group scope covers every project beneath it, so staging and production across a whole tree sit in one table.

environments
Staging and production across a whole group tree, with the commit that is live in each.

What you see

ColumnWhat it holds
projectWhich repository the environment belongs to
environmentThe environment name, such as production or review/feat-retry
stateAvailable or stopped
statusThe status of the deployment that is live
refThe branch or tag that is live
commitThe commit that is live
byWho deployed it
whenWhen that deployment finished

The ref and commit columns let you compare a live environment against a merge request you merged, in one table rather than two browser tabs. The status and actor columns separate a failed deploy nobody noticed from a successful one.

Selecting a row shows that environment's deployment history in the preview pane.

What you can do

KeyActionKeyAction
oopen the environment or review-app URLRre-deploy, or roll back
xstop an environmentvapprove a protected-environment deployment
Enterdeployment history in the previewYcopy the environment URL

R, x and v confirm inline in the footer, with the environment, the ref and the outcome named in full.

Review apps

o on a review-app row opens its URL in a browser. The URL comes from the environment itself, so a review app is one key from the merge request instead of a link dug out of a job log.

Scope and filters

b to a group or project, Tab to environments, then filter and pin:

You wantDo this
Production across the groupf name:production, P
Live review appsf name:review/* state:available, P
Failed deploymentsf status:failed, P