Kinsa finds buddybuild mobile CI/CD faster, easier and more reliable then Travis and Fastlane
The Kinsa mobile team needed a CI solution that would match the agility and speed of their development process and tried many solutions before settling on buddybuild.
When Jon Trainer, iOS lead at Kinsa, first started, they were using a Jenkins build server running on a mac mini for their iOS app. “Apart from the server itself being riddled with issues, the limited disk space, and time required to continuously update the keychain made the mac mini unusable. There was also a constant risk of spilling coffee on our build server, which added to the urgency of finding a new solution,” says Trainer.
Knowing it was too risky to continue relying on their in-house solution, Trainer started searching for alternatives. Based on peer recommendation, Trainer tried to craft a solution using Travis CI and a handful of Fastlane tools. Trainer hoped once they moved their main app over to these solutions, the team could productize their development pipeline with Travis and build with confidence in the cloud.
However, scripting Travis CI and fastlane together was cumbersome and didn't lend itself well to Kinsa's quick development speed. "Configuring fastlane with Travis felt like cobbling together a handful of tools, not a complete solution." says Trainer.
“It wasn’t an out of the box solution. We were quickly frustrated when trying to configure unit tests and schedule deployments to the QA team. We spent weeks trying to replace our Mac mini with a hosted CI service. We tried everything. They were all too complicated and server focused.”
Even after the initial set up, someone on the team was always on call to support the build infrastructure. “I remember spending most of a weeklong vacation with my family updating the scripts for Travis CI and fastlane,” says Trainer.
In looking for a CI solution, the Kinsa team needed something that was fast, dependable and optimized for mobile development. While on the same weeklong vacation, Trainer signed up for buddybuild, selected the repo he wanted to build and hasn’t looked for another CI solution since.
“What took weeks to set up with other CI solutions took hours with buddybuild. But the real differentiator has been that there’s no maintenance required with buddybuild,” says Trainer. Kinsa uses buddybuild to run unit tests, manage Apple Developer Portal accounts, schedule nightly deployments for their QA team and publish to the app store.
"For us, it's been an out of the box solution. Giving our team more time to build new features without having to worry about breaking our build infrastructure."
Since switching to buddybuild, the Kinsa team has adopted the platform for their Android app, and has triggered over 2000 total builds (and counting)!
Kinsa's favorite buddybuild features
Zero Configuration Setup No scripting or configuration files needed
Auto-Provision New Devices New users and their device UDID are auto-provisioned
Auto Deployments No processing time or review processes needed
The Kinsa team no longer needs to worry about scripting together tools or one-off solutions to build their continuous integration, delivery and development pipeline. Buddybuild is a complete solution that gives the Kinsa mobile team more time to build and iterate on new features.