TIL: Integrating Travis CI with iOS
It’s a self-proclaimed DevOps week, and I am slaying terminal commands.
Today I took on the challenge of integrating Travis with our iOS repo. Travis CI is a continuous integration tool that we already use with our web repo; each time a developer pushes to github, it runs tests. This ensures that when multiple developers are pushing to the same repository, no one is making changes that will break any existing features of our app. It seems trivial, but the consequences of this happening is dire. Catching breaking changes before pushes are live saves endless time, and Travis tells you exactly where to look.
Travis was already integrated with our github repository, and is friends with the fastlane, the tool I integrated yesterday.
I referred to this handy post that walked through how to set it up. Like all good integrations, it didn’t work quite as smoothly as plug & play.
A couple take-aways:
- I learned to specify the scheme of the workspace I wanted to test
- I learned to add a travis directory and .yml file, and execute a script
Doing two DevOps projects in a row is reinforcing a pattern (data set with an n of 2 is enough to extrapolate from right? ) — set up a file specific to the tool, which runs a script in the tool’s secret language. Tinker with the options until it’s just as you want it. And Boom. You never have to think about testing again…
Until you build a new feature and break the tests you wrote previously :)
