bitrise-webhooks

Sure! - Biggest difference is the reusable steps (e.g. add HockeyApp step, paste API token, good to go for deploy) - Generally being more open - steps/integrations, stacks, CLI, webhook service, workflow editor are all open sourced - Repository scanner - based on your configs you'll get a workflow to build, test and deploy your app in minutes - You can download the bitrise.yml to run your workflows locally with our CLI: http://devcenter.bitrise.io/bitrise-cli/ - Trigger map, to configure what to build when: http://devcenter.bitrise.io/webhooks/trigger-map/ - (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) - Codesigndoc - an open source t

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 ;)