Bitrise workflow details

⚠️ We're no longer using Bitrise as of November 2017.
This page only serves as documentation for legacy branches (pre-agua).

Here's the deal with Bitrise.

1. We avoid their GUI for workflow configuration as much as possible, in favor of using bitrise.yml files checked into the repository. The GUI workflow has been set to run:

• platform/ios/bitrise.yml for iOS builds
• platform/android/bitrise.yml for Android builds

1. If you want to change the bitrise.yml, do so and use the bitrise CLI tool (brew install bitrise or manual install) to bitrise validate.

2. Change the primary workflow in your branch to see how changes will be run on Bitrise before merging them to master, affecting all branches (since all branches run their respective primary workflow). You can create alternate workflows, named after branches, to have them run by commits in that branch, but generally we will just use primary.

3. You can also create custom non-branch-related workflows in the bitrise.yml beyond the default primary one, such as eventually where we will have a roll_build or similar workflow to address #2844.

4. Both [skip ci] and [ci skip] anywhere in commit messages work for our Bitrise setup for this repo as of f5bb746.

More on Bitrise's steps library (for example, we use the select-xcode-version, script, xcode-test, and slack steps): https://github.com/bitrise-io?utf8=✓&query=steps and http://www.steplib.com