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.
- Go to your app’s page on bitrise.io.
- Click the
- Find the
Service credential Usermenu. By default, the app owner is the Service credential User.
- Check the
Account Settings pageof 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.
Checking repository permissions and repository URL ⚓
- Make sure that you granted Bitrise access to your organization or team. It might be that you did not grant Bitrise access or denied access to the GitHub organization or Bitbucket team that owns the repository. See the Grant access to a GitHub Organization and the Grant access to a Bitbucket team guides for more information.
- Make sure the repository URL is up to date.
Go to the
Settingstab of your app on bitrise.io and make sure that the
Repository URLpoints to the current location of the repository. If, for example, you renamed or transferred your repository elsewhere, the status report can fail.
Bitrise Checks is a Github app which provides an extended version of the classic status checks Bitrise sends back to GitHub pull requests. Bitrise Checks include a Bitrise build summary...
Build logs allow users to analyze their builds and find out what went wrong - and what went right! On Bitrise, build logs are easily accessible: they can be viewed...
Access our build machines remotely when running a failed build again. You can use either SSH or a screenshare app to log in to the build's virtual machine.