98% deployment success-rate with Aviator MergeQueue

Team Size

developers

Structure

Monorepo

CI Runtime

Deploys

5 per day

Featured integration

MergeQueue

Airspace

Airspace Case Study | Aviator

Read how Airspace has achieved a 98% deployment success rate with Aviator MergeQueue and about their approach to implementing the developer collaboration suite.

"We used to have this heavy QA process, manual deploys. Originally, we would merge our PRs and then run a bunch of tests. If all the tests passed, then we would deploy. Now, we now run all the tests on the PR before we merge.

Requesting to merge created a bottleneck, and I knew it would start building up as we scaled to more deployments.

We knew it’d be an issue to fix. We took a couple of surveys internally, and some teams couldn’t wait to use Aviator.

One of the other big driving factors was to help our budget. We calculated that it’d cost $8 to run all of our tests on one PR because the codebase didn’t allow for checking code that’s changed."

Challenge

The team was in a weird spot, as the need for a merge queue hadn’t been a priority. However, constantly restarting end-to-end tests was bogging down their CI/CD pipeline. It became apparent that a merge queue was necessary in order for frequent deployments to work.

Airspace

Airspace Case Study | Aviator

Integration

Michael and team originally weren’t using CI/CD pipelines. After setting them up, the team quickly found the need for a merge queue to scale deployments. It took less than a day to create a proof of concept that gave the team context on how Aviator MergeQueue reacts with their primary repository.

Airspace

Airspace Case Study | Aviator

"I came along, rolled up my sleeves and said, we got to get on CI/CD. So I set up some things and quickly realized like, wait a second. There's a need for a merge queue now.

We've made a couple of little config tweaks to Aviator here and there. What I really enjoy is it's almost like you set it up and forget about it.

We were in this weird spot too, cause we didn't actually need Aviator quite yet, but I was preparing my team before queuing issues became unsustainable."

"After Aviator, we have a pretty high success rate for deployments. I like Aviator because it has good visibility and UI,.
And support has been great. I can't stress how important that is from a business perspective, especially when you have a hundred things going on and then you get stuck and you don't hear from support for three or four days."