All the webhooks you need

If you already have webhooks set up for your apps on Bitrise and you are happy with them, you still might be interested in how generalizing our webhook processing logic can make your life better.

If you already have webhooks set up for your apps on Bitrise and you are happy with them, you still might be interested in how generalizing our webhook processing logic can make your life better.

What's new?

The new webhook processor supports new providers, now it's possible to set up not just GitHub, Bitbucket, but Visual Studio Online and GitLab webhooks as well. It's not even the end of the story, because all the logic has been open sourced and exposed to a separate service.

The point of this update was to make it possible to connect any kind of webhooks and map them to our build trigger API. That's how delightful features like starting your build with a Slack message could born. The number of possibilities are close to infinite, but we tried to figure out what's the most important for you. Read on to check out the list of currently supported services.

We also introduced API tokens to the webhook URLs. It means that the v1 requests missing the token are now deprecated. The new format is ../h/{provider}/BITRISE-APP-SLUG/BITRISE-APP-API-TOKEN. Read more about this in the webhooks GitHub repo.

Supported services

If you'd like to set up a new webhook for your already existing app right away, go to your app's Code tab and check the Webhook section for auto-generated webhook URLs after selecting the desired service.

GitHub

It's been there already and it stays still. One thing has changed: now you are able to see the code behind it.

Bitbucket v2

Bitbucket has been already supported, check the docs on GitHub for setup instructions.

Visual Studio Online

It's a new addition, for people using Xamarin and having their code hosted on VSO. Check out how to set it up in the related description.

GitLab

It's our latest addition, check out how to set up a Bitrise webhook for your GitLab repository.

Slack

That's something showing the real power of this change. You can set it up easily from your Slack account as an outgoing webhook, or a slash command, like /bitrise branch: master. Read more about how to add it to your Bitrise app in the webhooks Readme.

Anything else?

The greatness of open source does not lie in transparency exclusively. For us it's also about letting people customize their workflows in their favor. We think that hosting technology is great, but giving the chance to integrate with any kind of service is priceless.

If you have something you'd use and we don't have its support implemented currently, you can open an issue in the webhooks repo anytime. If you feel the power, you can send a pull request right away! Check out our guide on how to add a new service to the webhooks processor.

If you have any questions, join our public Slack, or tweet us @bitrise we are more than happy to help!

No items found.
The Mobile DevOps Newsletter

Explore more topics

App development

Best practices from engineers on how to use Bitrise to build better apps, faster.

Community

Meet other Bitrise engineers, technology experts, power users, partners and join our BUGs.

Company

All the updates about Bitrise events, sponsorships, employees, and more.

Insights

Mobile development, latest tech, industry insights, and interviews with experts.

Mobile DevOps

Learn why mobile development is unique and requires a set of unique practices.

Releases

Stay tuned for the last updates, new features, and product improvements.

The Mobile DevOps Newsletter

Join 1000s of your peers. Sign up to receive Mobile DevOps tips, news, and best practice guides once every two weeks.