Skip to content
Start a conversation

WorkVu.City

Automation on a startup budget

Build and deploy issues dropped to zero once each team owned a pipeline.

0
Build and deploy issues afterwards

A small company was shipping by hand. A lot of the code that produced data was not in source control, and work was thrown over a wall for someone else to release. We put CI/CD in place and made ownership concrete.

The problem

Builds, deploys, and data jobs depended on people remembering the steps. APIs, data, and services were not versioned.

Teams handed work to each other for testing and release. Fixing a bad deploy meant logging into a machine.

What we did

Source control became mandatory, including the scripts that generated data. Each project got a CI/CD pipeline the owning team could run.

Access to deploy by hand on remote machines was removed, so the only path to production was the pipeline. Services grew versioned contracts instead of informal handoffs.

What changed

Incidents caused by builds and deploys stopped. Teams started treating each other as consumers of an API, with a version, rather than as the next person in a queue.