Rollbar Lines · Results
We built it to run our own engineering.
Rollbar Lines works our backlog every day. It writes features, removes feature flags, reviews every pull request our engineers open, and reproduces bugs from our own error data. We publish the numbers from our own repositories, along with what one of our teams saw before and after.
Case study
We gave it to one of our own teams and measured the before and after.
The team is twelve people, engineers, designers, and a product manager. Every ticket went down the same line. A virtual machine came up, the tests ran, a pull request came out, and one of them approved it.
Throughput
Merged pull requests per week rose 3.5x over eight months with no added headcount. Rollbar Lines wrote 35% of what merged.
Cycle time
The slowest quarter of pull requests took about 47% less time to merge over the same eight months, and the median stayed under a day. The agent’s pull requests arrive with the tests already run and the report already written.
Review coverage
Every pull request your engineers open gets a review that names the files it followed and the checks it skipped. In the case study, reviews went from a handful a month to about twenty a day once Rollbar Lines reviewed everything automatically.
Everyone could ship.
Even our product manager wrote the tickets and Rollbar Lines wrote the code. By month seven he was merging as many pull requests as anyone on the team, 15-20 per week, most of them written by Rollbar Lines from his tickets.
Case study figures were measured from our own code host across three repositories, comparing two-week windows eight months apart.
How we use Rollbar Lines
Rollbar Lines has worked our backlog for nearly six months.
271
pull requests authored across 21 of our repositories in under six months
157
merged by our engineers after review
19 of 100
web app pull requests written by Rollbar Lines, third behind two engineers
28 of 100
API pull requests written by Rollbar Lines
What the numbers add up to
Both stories come from the same line, with a person approving every merge.
The team shipped more without hiring.
One team’s merged pull requests per week rose 3.5x in eight months with the same people, and Rollbar Lines wrote 35% of what merged. At Rollbar it wrote 271 pull requests across 21 repositories in under six months, and our engineers merged 157 of them.
Slow pull requests got faster.
The slowest quarter of pull requests merged about 47% sooner over the same eight months, and the median stayed under a day. Reviews went from a handful a month to about twenty a day once Rollbar Lines reviewed every pull request.
A person approved every merge.
Each of those merges went through an engineer on the team who read the diff, the report, and the review first. Rollbar Lines has no path to the main branch, at Rollbar or anywhere it is installed.
Using Rollbar Observability metrics, one of our fixes took an error with 24K occurrences a day to 0 minutes after the deploy and has not come back. A feature built with Rollbar Lines saw a 6% adoption rate in the first week with manual checks in Mixpanel.
Get the same results with the team you already have.
We will show you where the first line goes.
Set up a demo, or talk with a Rollbar engineer about where the same line would fit in your team. We will walk you through a real run, start to pull request, and show you which of your tickets it would take first.