Member-only story

Why I use Continuous Integration for my iOS App

Jay Wilson
3 min readJul 23, 2021

Photo by Zan on Unsplash

All this year, I’ve been using BitRise for iHog. Let me tell you, this has been amazing. Here are my top 3 reasons why I like continuous integration, CI. This can be done with generally any CI ⁠tool, but I used BitRise because I had previously heard about them on podcasts and have seen their ads. They are also mobile focused, which gave me a really good feeling choosing them.

Incrementing build numbers⁠

I can’t be the only iOS developer that has forgotten to change the build number to push a build to TestFlight. With CI, I will never forget again. I was able to configure a step in the workflow to change the build number in the Xcode project to match Bitrise’s build number. This means that the build number will always be more than the one before it.

The step that changes the Build Number.

I also didn’t have to build the step myself. Bitrise had it already to go as a step where I just had to pass it the version number.

Testing in the “cloud”

Every time I push code to the GitHub repo, the tests run. This makes sure that I’m testing often, even if I don’t have time to test before I have to do the next…

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Jay Wilson
Jay Wilson

Written by Jay Wilson

I like to solve problems using Swift, make YouTube videos, and take photos. I also really enjoy a good cup of coffee.

No responses yet

Write a response