Reporting the build status to your Git hosting provider

Bitrise can push back build status reports to your Git provider (GitHub/GitLab/Bitbucket). You only need to authenticate Bitrise to communicate towards the Git hosting service. Apart from build status reports, this enables other operations, such as auto-registering SSH keys or Webhooks.

To do this, you need to specify a Service Credential User on the Team tab of your app on bitrise.io. You also need to make sure that this user has a connected account with the git hosting service of your choice on bitrise.io. This account will be used by Bitrise to communicate with the API of the git hosting provider.

Status reports are for automatically triggered builds only

Status reports are sent only for automatically triggered builds, such as builds triggered by a code push or a pull request.

Make sure the account you wish to use is connected to the relevant hosting provider: go to the Account settings page of the account and check the CONNECTED ACCOUNTS menu on the left side.
Go to the Team tab of your app on bitrise.io.
Find the Service credential User menu and select the user with the connected account.
Click the Test the Git connection button to make sure the selected user’s connection can be used for sending back the build status to the hosting provider.

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.

You can schedule your builds to run automatically at a specific time of the week so that you can check your logs when it's most convenient for you.

Environment Variables (Env Vars) consist of a key and a value, as well as optional attributes. They can be defined on the level of apps, Workflows or Steps.