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 many of the growth platforms and languages, it is deeply built-in with GitHub, so it might probably enable you 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 probably the greatest help for cellular growth initiatives, however you need to use the platform to automate something from desktop apps to server-side initiatives.

A serious distinction between the 2 providers is that Travis solely works with GitHub, whereas Bitrise helps mainly each git internet hosting supplier available on the market. You should use your individual personal 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 mainly steps chained collectively in a given order. There are many accessible steps as a part of the Bitrise infrastructure, they’re very nicely documented, and actually highly effective.

Since Travis has a deep integration with GitHub, you’ll be able to arrange the continual integration surroundings in your apps very quickly. Shifting to Bitrise requires a bit bit extra effort. That may be a ache level for some folks, however there are many articles and video tutorials concerning the fundamental setup.

Organising Bitrise is tremendous straightforward!

I’ll simply present you a fast walk-through, so you’ll be able to see that Bitrise can be very straightforward to make use of and it helps all the most important git service suppliers and software templates. First, it’s important 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, it’s important to choose an proprietor and specify the entry degree of your model new app (personal or public). Subsequent, it’s important to join your git repository (GitHub, Bitbucket, GitLab or handbook connection) and supply the mandatory credentials, so the CI course of can take a look at the supply code, from the given department.

Bitrise will then validate every little thing, it even scans your venture and provides you a main 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 it’s also possible to arrange a unique workflow if these will not suit your wants.

Let’s assume that you’ve an iOS app, in order a ultimate step you’ll be able to customise a number of extra issues like venture path, scheme title, export technique, construct stack (macOS & Xcode model). Optionally you’ll be able to register a webhook, to make Bitrise mechanically begin a construct each time “one thing” occurs inside your repository.

No extra config recordsdata

You possibly can 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 consider it is 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’ll be able to 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, but it surely has a big impact on the DX. 🤓

If you would like to run Bitrise domestically, you’ll be able to set up the Bitrise CLI instruments by way of brew, however in an effort to make it work, it’s important to create an area bitrise.yml configuration file to declare your workflow.

I do not need to get an excessive amount of into the workflow setup particulars, as a result of there are nice tutorials about the best way to setup & fantastic tune them. Let’s simply say that you would be able to safely configure every little thing by utilizing the built-in workflow editor.

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

Automated standing test 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 must arrange the correct webhooks & set off mechanism to make it work. If you happen to skipped the automated webhook setup on the Create New App display you’ll be able to nonetheless allow it on the Code tab. 🔨

Webhooks could be registered mechanically for GitHub, Bitbucket or GitLab for those who grant entry to those service suppliers on the Account settings web page. In any other case, you’ll be able to 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 Staff 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 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 in case you are utilizing GitHub, an automatic standing test report shall be accessible immediately on the pull request web page.

You possibly can bind all of the accessible 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 could be configured contained in the workflow editor beneath the Triggers tab. 🔫

Conclusion

Congratulations, you simply realized the essential strategy of migrating an iOS venture from Travis to Bitrise. As you’ll be able to see the toughest a part of the entire switch process is the preliminary venture arrange, however that is fairly unavoidable in case you are changing your CI supplier. Bitrise could be built-in to GitHub and it might probably do the very same checks too.

I consider that in case you are searching for a superb different for Travis, it’s best to positively attempt Bitrise. I can not emphasize sufficient how highly effective is the step based mostly workflow setup strategy. Bitrise is versatile, characteristic wealthy, has an incredible help staff and most significantly it is ridiculously straightforward to be taught. Strive Bitrise now! 😉