Find out how to migrate your iOS app from Travis CI to Bitrise?

Travis vs Bitrise

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

Bitrise is a common steady integration and supply service. It has the most effective help for cell improvement tasks, however you should use the platform to automate something from desktop apps to server-side tasks.

A significant distinction between the 2 companies is that Travis solely works with GitHub, whereas Bitrise helps mainly each git internet hosting supplier in the marketplace. You should use your personal non-public git repository too.

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

Since Travis has a deep integration with GitHub, you may arrange the continual integration atmosphere 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 in regards to the primary setup.

Organising Bitrise is tremendous straightforward!

I’ll simply present you a fast walk-through, so you may see that Bitrise can also be very straightforward to make use of and it helps all the most important git service suppliers and utility templates. First, you must 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 means.

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

Bitrise will then validate every little thing, it even scans your challenge and offers you a major workflow primarily based 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 also 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 may customise a number of extra issues like challenge path, scheme title, export technique, construct stack (macOS & Xcode model). Optionally you may register a webhook, to make Bitrise robotically begin a construct each time “one thing” occurs inside your repository.

No extra config information

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 combined with the precise codebase.

I imagine this can be a enormous 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 may squash & rebase, however actually, 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 big impact on the DX. 🤓

If you would like to run Bitrise regionally, you may set up the Bitrise CLI instruments by means of brew, however so as to make it work, you must 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 the way to setup & tremendous tune them. Let’s simply say which you could safely configure every little thing by utilizing the built-in workflow editor.

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

Computerized standing test on GitHub pull requests

Checking GitHub pull requests is among the greatest options of Travis CI. Bitrise can do the very same factor, you simply should arrange the correct webhooks & set off mechanism to make it work. For those who skipped the automated webhook setup on the Create New App display you may nonetheless allow it on the Code tab. 🔨

Webhooks may be registered robotically for GitHub, Bitbucket or GitLab should you grant entry to those service suppliers on the Account settings web page. In any other case, you may 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 Group Companies (Code Push, Tag Push)
• Slack (Outgoing Webhook & Slash Command)
• Gogs (Code Push)
• Deveo (Code Push, Tag Push)
• Assembla (Code Push)

After the webhook is related it is possible for you to to set off builds primarily based on supported occasions listed above within the brackets. The great factor is if you’re utilizing GitHub, an automatic standing test report can 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 particular check workflow. These set off maps for the git repository occasions may be configured contained in the workflow editor underneath the Triggers tab. 🔫

Conclusion

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

I imagine that if you’re on the lookout for a very good different for Travis, you must positively attempt Bitrise. I can not emphasize sufficient how highly effective is the step primarily based workflow setup strategy. Bitrise is versatile, characteristic wealthy, has a tremendous help group and most significantly it is ridiculously straightforward to study. Strive Bitrise now! 😉