Deployments
Deployments answers two questions: what is running in each environment right now, and how did it get there.
It observes. Taiga records and reports deployments; it does not perform them. Your pipeline stays where it is, and Taiga reads what it did.
What is running where
Section titled “What is running where”The top of the page is a ladder of your environments, one card each, in order. Each shows the deployment currently live there and any deploy still in flight.
Current is derived from your deployment history rather than taken from a provider’s “active” marker, because that marker is not reliable enough to build a page on. What you see is the most recent deployment that actually succeeded.
The history
Section titled “The history”Below the ladder is every deployment, in one list rather than split per environment.
It includes deployments Taiga performed and deployments it mirrored from your provider, so the record does not have a hole in it for work that happened outside Taiga. You can filter by environment, status, branch or tag, and who triggered it.
Verification and preview records are hidden by default. They are real deployments but they are noise when you are asking what shipped, so they are opt-in.
If you connected a repository that already had deployment history, importing it backfills the record rather than starting your history at the day you signed up. Importing is an administrator action, since it reaches into the connected provider; reading the history is not.
Delivery metrics
Section titled “Delivery metrics”The Insights tab derives the four standard delivery metrics from that history:
| Metric | What it tells you |
|---|---|
| Deployment frequency | How often you ship. |
| Lead time | How long a change takes to reach production. |
| Change-failure rate | What proportion of deployments cause a problem. |
| Time to restore | How quickly you recover when one does. |
They are computed, not entered, which is the point. Metrics that require someone to maintain a spreadsheet stop being maintained.
Where there is not enough history to say something honest, Taiga says so rather than showing a number derived from three data points.
Environments come first
Section titled “Environments come first”An environment is what a deployment is recorded against, so the ladder is only as good as the environments you have defined.
Environments and the cloud connection behind them live in project settings, not on this page. Set them up before expecting this surface to tell you anything.