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.

Configuring build status reporting

  1. Make sure the account you wish to use is connected to the relevant hosting provider: go to the Profile settings page of the account and check the CONNECTED ACCOUNTS menu on the left side.

    Reporting the build status to your Git hosting provider
  2. Go to the Team tab of your app on bitrise.io.

  3. Find the Service credential User menu and select the user with the connected account.

    Reporting the build status to your Git hosting provider
  4. 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.

Troubleshooting build status reporting

If your builds do not send status reports to your git hosting provider - GitHub, GitLab or Bitbucket -, you will need to do a little investigating to find out what causes the problem. Let’s take a look at the potential issues!

Checking the service credential user

The Service credential User of the app on bitrise.io must have a connected account to the git hosting provider.

  1. Go to your app’s page on bitrise.io.

  2. Click the Team tab.

  3. Find the Service credential User menu. By default, the app owner is the Service credential User.

  4. Check the Account Settings page of the account of the Service credential User.

On the left side you can find the Connected Accounts section, where you can connect and disconnect other services (like GitHub, Bitbucket or GitLab) to your bitrise.io account.

Make sure you connected the correct account

If you have more than one account with the given service, you should also check whether you connected one that can access the repository. You can check which user you connected by clicking the name of the service provider on your bitrise.io Account Settings page. It will open the connected user’s page on the website of your git hosting provider.

Make sure that the Service credential User has administrative rights to the repository. Check this on the repository settings on the website of your git hosting provider.

Checking repository permissions and repository URL

  • Make sure that you granted Bitrise access to your Workspace or team. It might be that you did not grant Bitrise access or denied access to the GitHub Workspace or Bitbucket team that owns the repository.

  • Make sure the repository URL is up to date. Go to the Settings tab of your app on bitrise.io and make sure that the Repository URL points to the current location of the repository. If, for example, you renamed or transferred your repository elsewhere, the status report can fail.