Fhmobsdk 20.travis.build

[corinnekrych]

This PR is for to support travis build

• add travis.yml
• share FH schema
• make unit tests passed in travis environment (vendorId is null in such env)

@cvasilak @wei-lee mind to review?

[wei-lee]

@corinnekrych this looks good. Can we use travis to publish to Coacoapod automatically?

[corinnekrych]

@wei-lee @cvasilak you can do lot of things with travis, like running post/pre script etc... But I wonder do we really want to automatize the release to cocoapods? Usually we do the push to cocoapods just before releasing a new version not for each PR. what is your intend?

[wei-lee]

@corinnekrych You are right, we are not intending to do a new release for every PR. I am wondering if we can do a release when a new tag is pushed, like what we did for the android sdk. This way we don't have to run any script manually, all we have to do is to push a tag. WDYT?

[corinnekrych]

Ah! that is clever let me dig in more closely @wei-lee

[corinnekrych]

@wei-lee After further investigation it's not possible to automate the release process on cocoapods. since version 0.33, releasing pod goes through Trunk (https://guides.cocoapods.org/making/getting-setup-with-trunk.html). As a prerequisites, before releasing you need to register. The registration process is associated to a computer ("You do not have a password, only a per-computer session token.") and required an async email validation.

The release process as described in https://cocoapods.org/?q=FH could automate b and c part (gihub release and doc generation) with gh token (for auth) and some more scripting. we can track that part with a different ticket to discuss further.

[cvasilak]

@wei-lee After further investigation it's not possible to automate the release process on cocoapods. since version 0.33, releasing pod goes through Trunk (https://guides.cocoapods.org/making/getting-setup-with-trunk.html). As a prerequisites, before releasing you need to register. The registration process is associated to a computer ("You do not have a password, only a per-computer session token.") and required an async email validation.

sounds reasonable

The release process as described in https://cocoapods.org/?q=FH could automate b and c part (gihub release and doc generation) with gh token (for auth) and some more scripting. we can track that part with a different ticket to discuss further.

+1 let's track it separate and look further if we can get more automation on the release process

[cvasilak]

:eyes: on it

[cvasilak]

tested on experimental travis build, and got green :green_heart: flag https://travis-ci.org/cvasilak/fh-ios-sdk/builds/59375004

:+1: to merge.

[corinnekrych]

I've created:

• FHMOBSDK-65 to further automate process
• FHMOBSDK-66 to run the build on a matrix (iOS7, iOS8) like the android travis is doing. Other PRs will come. @wei-lee Good to merge?

[wei-lee]

@corinnekrych :+1: