The best way to migrate your iOS app from Travis CI to Bitrise?

Travis vs Bitrise

Travis is all about testing open supply initiatives hosted on GitHub. It helps a lot of the growth platforms and languages, it is deeply built-in with GitHub, so it might assist you to pace up your code evaluate course of (Hazard) by the automated PR remark system.

Bitrise is a common steady integration and supply service. It has among the best assist for cell growth initiatives, however you should utilize the platform to automate something from desktop apps to server-side initiatives.

A significant distinction between the 2 companies is that Travis solely works with GitHub, whereas Bitrise helps principally each git internet hosting supplier available on the market. You need to use your individual non-public git repository too.

In comparison with Travis, there isn’t a such factor as a job lifecycle. Bitrise makes use of steps as atomic constructing blocks. Each single construct process is a step. Workflows are principally steps chained collectively in a given order. There are many out there steps as a part of the Bitrise infrastructure, they’re very effectively documented, and actually highly effective.

Since Travis has a deep integration with GitHub, you possibly can arrange the continual integration setting to your apps very quickly. Transferring to Bitrise requires a bit of bit extra effort. That may be a ache level for some folks, however there are many articles and video tutorials concerning the primary setup.

Organising Bitrise is tremendous simple!

I’ll simply present you a fast walk-through, so you possibly can see that Bitrise can be very simple to make use of and it helps all the main git service suppliers and software templates. First, you need to log in (or register a free account). To create a brand new app click on the Add App menu merchandise and the wizard will information you thru each step in a user-friendly method.

As a primary step, you need to choose an proprietor and specify the entry stage of your model new app (non-public or public). Subsequent, you need to join your git repository (GitHub, Bitbucket, GitLab or guide connection) and supply the mandatory credentials, so the CI course of can try the supply code, from the given department.

Bitrise will then validate the whole lot, it even scans your undertaking and provides you a major workflow based mostly on the code (detected) inside your repository. iOS, Android, Xamarin, fastlane, macOS, Cordova, Ionic, React Native, Flutter are the built-in ones, however you may as well arrange a unique workflow if these will not suit your wants.

Let’s assume that you’ve got an iOS app, in order a closing step you possibly can customise a number of extra issues like undertaking path, scheme identify, export methodology, construct stack (macOS & Xcode model). Optionally you possibly can register a webhook, to make Bitrise routinely begin a construct each time “one thing” occurs inside your repository.

No extra config recordsdata

You’ll be able to safely take away the hidden .travis.yml file out of your repository, you will not want that anymore. At Bitrise each configuration is saved as a part of the service, so the CI associated stuff will not be blended with the precise codebase.

I imagine this can be a big benefit in comparison with different suppliers as a result of you do not have to pollute your git historical past with ineffective ‘modified ci file once more’ commits. I do know you possibly can squash & rebase, however truthfully, I like the way in which how Bitrise handles this as part of the service infrastructure. It is only a small factor, nevertheless it has a huge effect on the DX. 🤓

If you would like to run Bitrise domestically, you possibly can set up the Bitrise CLI instruments by way of brew, however with a view to make it work, you need to create an area bitrise.yml configuration file to declare your workflow.

I do not wish to get an excessive amount of into the workflow setup particulars, as a result of there are nice tutorials about easy methods to setup & wonderful tune them. Let’s simply say that you may safely configure the whole lot through the use of the built-in workflow editor.

Though I might spotlight one factor, that is enabled on Travis by default…

Automated standing verify on GitHub pull requests

Checking GitHub pull requests is likely one of the finest options of Travis CI. Bitrise can do the very same factor, you simply should arrange the right webhooks & set off mechanism to make it work. Should you skipped the automated webhook setup on the Create New App display screen you possibly can nonetheless allow it on the Code tab. 🔨

Webhooks will be registered routinely for GitHub, Bitbucket or GitLab should you grant entry to those service suppliers on the Account settings web page. In any other case, you possibly can join webhooks for the next instruments manually:

• GitHub (Code Push, Pull Request, Tag Push)
• Bitbucket Webhooks (Code Push, Pull Request, Tag Push)
• Bitbucket Server Webhooks (Code Push, Pull Request, Tag Push)
• GitLab (Code Push, Merge Request, Tag Push)
• Visible Studio On-line / Visible Studio Crew Providers (Code Push, Tag Push)
• Slack (Outgoing Webhook & Slash Command)
• Gogs (Code Push)
• Deveo (Code Push, Tag Push)
• Assembla (Code Push)

After the webhook is linked it is possible for you to to set off builds based mostly on supported occasions listed above within the brackets. The good factor is if you’re utilizing GitHub, an automatic standing verify report might be out there instantly on the pull request web page.

You’ll be able to bind all of the out there occasions to construct actions, for instance, a pull request from the dev supply department to the grasp goal department can set off a selected take a look at workflow. These set off maps for the git repository occasions will be configured contained in the workflow editor below the Triggers tab. 🔫

Conclusion

Congratulations, you simply realized the fundamental strategy of migrating an iOS undertaking from Travis to Bitrise. As you possibly can see the toughest a part of the entire switch process is the preliminary undertaking arrange, however that is fairly unavoidable if you’re changing your CI supplier. Bitrise will be built-in to GitHub and it might do the very same checks too.

I imagine that if you’re on the lookout for a very good different for Travis, it is best to undoubtedly strive Bitrise. I am unable to emphasize sufficient how highly effective is the step based mostly workflow setup method. Bitrise is versatile, function wealthy, has an incredible assist crew and most significantly it is ridiculously simple to study. Attempt Bitrise now! 😉