Most source code hosting service provides a feature to register webhooks. A webhook is basically an URL which will be called on specified events.
To have Bitrise automatically start a build every time you push code into your repository you can set up a webhook at your code hosting service which will automatically trigger a build on Bitrise with the code you push to your repository.
Setting up incoming webhooks automatically ⚓
There are two ways to automatically set up an incoming webhook:
- When adding a new app.
- On the
Codetab of the app.
If you select
Bitbucket as the source code provider when you add your app Bitrise automatically sets up a webhook for it with a click of a button at the end of your app setup journey. In this case, you can skip this tutorial.
Adding a webhook automatically when adding an app ⚓
If you select
Bitbucket as the source code provider when you add your app Bitrise automatically sets up a webhook for it with a click of a button at the end of your app setup journey.
Adding a webhook automatically on the Code tab ⚓
You can automatically register a webhook to the repository on the
Code tab of the app. This requires:
- That you have admin rights to the repository.
- That the account that hosts the repository is connected to your Bitrise account.
Open your app on bitrise.io and go to the
INCOMING WEBHOOKS section and click
Setting up incoming webhooks manually ⚓
You can manually setup or change your webhooks after you registered your application.
You can find the supported providers in your application’s
Code tab. Choose the
SETUP MANUALLY option to set up a webhook with any of the supported providers.
Our webhook processor is Open Sourced. If you are looking for a not supported solution, you can create an issue on the GitHub page or create a pull request with the implementation. You can also run your own webhook provider behind your own firewall if required.
You can find detailed description about the setup on the Code tab or select a provider to check its devcenter article:
- Adding a GitHub webhook
- Adding a Bitbucket webhook
- Adding webhooks for Gitlab
- Adding webhooks for Visual Studio Online / Visual Studio Team Services
- Adding webhooks for Slack
- Adding webhooks for Gogs
- Adding webhooks for Deveo
- Adding webhooks for Assembla
Setting up outgoing webhooks ⚓
You can also set up outgoing webhooks on Bitrise. With these, Bitrise can notify any selected service about your build events. A build event is:
- When a build is started.
- When a build ends.
See the Webhook Troubleshooting guide for webhook related troubleshooting / debugging notes.
You can trigger and abort builds with the Bitrise API. Define parameters for the build: for example, branch, tag or git commit to use. Custom environment variables can be defined...
Both incoming and outgoing webhooks can be set up with the Bitrise API. They are important for automatic build triggering and the reporting of build events to other services.
If you need to, you can skip a specific commit or pull request. Skipping means, in this context, that a code change will NOT trigger a build on Bitrise, even...