[birmacher]

With Travis you have to use their yml and reimplement your whole configuration per app every time. On Bitrise with the reusable integrations you can simply just drag & drop more than 100 integrations like HockeyApp and with only adding your API token you are ready to go. However we also have the YML file and an open source CLI, so you can run the same thing locally. Also when you add your app to Bitrise we will scan it and instantly give you a workflow that builds, tests and deploys your app.

[viktorbenei]

Couple of additional things:

- Local CLI / runner: http://devcenter.bitrise.io/bitrise-cli/

- Trigger Map, to configure what to build when: http://devcenter.bitrise.io/webhooks/trigger-map/

- Linux/Android image available as an open Docker container: http://devcenter.bitrise.io/docker/run-your-build-locally-in...

- Open source, offline workflow editor (UI, beta): https://discuss.bitrise.io/t/offline-workflow-editor-workflo...

- (GitHub,) Bitbucket and GitLab (full API) support, and additional webhook support for Slack (trigger a build from Slack), visualstudio.com, gogs, deveo git repos through the open source Webhook processor (https://github.com/bitrise-io/bitrise-webhooks) - the last two were contributed by the community ;)

[baronofcheese]

Would also seem that Travis doesn't have Xamarin support, or so it appears.

[birmacher]

Yup, that's correct :) Also if you are comparing us to Travis, we have both Bitbucket & GitLab integrations in addition to GitHub.

Our build machines are faster to use, too, because the most used VMs are pre-booted, which saves 1-2 minutes.