≡    File   Edit   View   Run   Help

● READY

~ $ ./present

TERMINAL LABS · LAUNCH DAY

Terminal

One command from merge to production. Version 2 is here.

~ $

Presented by {{author}}

On the menu today

↑ ↓ select · ENTER open

 

MAIN MENU

1

Why we rebuilt it

Releases that broke on a Friday

2

What's new in v2

One command, five steps

3

Moving your pipeline

A config file, not a migration

4

What comes next

The road to version three

PART 01

Why we rebuilt it

THE PROBLEM

Shipping should take one command, not one afternoon.

Most teams still release by hand. Terminal turns build, test, deploy and rollback into one line anyone can run.

~ $

~ $ cat notes.txt

Where releases go wrong

Releases fail in the gaps between tools. Someone skips a step, a script assumes the wrong branch, or the one person who knows the rollback is on holiday. We read two hundred incident reports from beta teams, and almost none came from bad code. They came from a process that lived in somebody’s head.

[{{#}}/{{total}}]

Version 2 at a glance

 

WHAT’S NEW IN V2

  • One command runs build, test, deploy and verify
  • Rollback plans are written before you ship
  • Every release leaves a plain-text log
  • Works with the CI you already have

[{{#}}/{{total}}]

 

12K

teams shipping with the beta

 

38s

median time from merge to live

 

4×

more releases each week

Six months in beta

Source: Terminal Labs beta telemetry, past six months

One command, every step

Add a release file to your repo, then run one command from any branch. Every step prints as it happens.

 

bash — 80×24

$ terminal release --env prod
✔ build     dist/ in 41s
✔ test      218 passed
✔ deploy    3 regions
✔ verify    health checks green

Released v2.4.1 in 1m 52s
Undo with: terminal undo

Three commands to learn

 

terminal release

Ship it

Builds, tests and deploys the current branch, then checks that it’s healthy.

F1

 

terminal undo

Roll it back

Restores the last good release in seconds and logs the reason.

F2

 

terminal log

Read the story

Shows every step of every release, who ran it and what changed.

F3

The road to v3

 

v2.0 · NOW

One-command releases and instant rollback

v2.1

Release previews for every pull request

v2.2

Approvals from chat, logged with the release

v3.0

Several services shipped as one plan

 

[ no signal ]

release-log.png

A release log you can actually read

Every run writes a plain-text log: what changed, who shipped it, how long each step took and how to undo it.

~ $ fortune

We used to plan releases around lunch. Now we do six before it.

--

Priya Raman
Platform lead, Larkspur Health

~ $

The people behind the prompt

~ $ who

 

[ photo ]

tty1

Ada Kowalski
Founder, core CLI

 

[ photo ]

tty2

Tomás Reyes
Release engine

 

[ photo ]

tty3

Leila Farouk
Docs and DX

 

[ photo ]

tty4

Sam Whitfield
Infrastructure

Thanks. Now go ship something.

hello@terminal.example
+1 555 0148 · terminal.example

~ $

 F1  Help     F5  Replay     F10  Quit