Repository connection issues

Buddy uses your integration details to refresh the synchronized project as soon as it receives a webhook from the Git service hosting the repository. If the credentials to the repository are valid and the webhook has successfully reached the service, Buddy will run git fetch and clone the repository to the pipeline filesystem.

Error

Commits pushed to synchronized repositories do not appear in Buddy and do not trigger associated pipelines.

Possible solutions

1. Refreshing repository

If you encounter this problem for the first time, in 9 out of 10 cases refreshing the repository manually will help.

Go to the Repository tab in Project settings and click Refresh now:

Refreshing repositoryRefreshing repository

This kind of problem is usually caused by a networking issue between the Git provider and Buddy.

Checking provider status

If the problem persists, you can check the provider for possible downtime on their status page:

2. Re-adding desynchronized project

If you don’t see the Refresh repository tab, it means that somebody in the workspace changed the Git provider to Buddy. This means that the repository is no longer synchronized with the original Git hosting service.

It is not possible to change the synchronization method back to the original Git provider – you need to add a project once again and clone the pipelines to it.

3. Debugging connection events

If refreshing the repository manually no longer helps and you are sure your Git provider is up and running, go to the Activity tab in the project and look for the following event:

Connection errorConnection error

If you find such event on the list, click on it to expand the details:

Error detailsError details

There can be many types of errors there. The most common reasons the integration doesn’t work are:

  1. Expired token – in this case, go to the Integrations tab, click the name of the integration that was used to synchronize the project, and click Refresh OAuth token
  2. No access to the project or limited rights – this means that the user who added the integration has no access rights to the project in the selected Git provider
  3. The name of the project/URL has changed or it has been transferred to another organization etc. – to solve it, go to the Code tab in the project settings, click Change repository connection, re-configure the project to the desired details in the Repository tab, then click Change when ready.

Make sure to select Clone repository from scratch before hitting Refresh in the final step.

4. Checking webhooks status

If you updated the integration and the project but new commits still don’t appear in Buddy, go to the Activity tab in the project and see if there are any new push events with your commits. If you are sure there are no events there, go back to Code > Repository and check the Refresh webhook logs section.

  1. If you can’t see any information about new webhooks, refresh the repository manually as in step 1.
  2. If this problem persists for a long time, go to the project options on GitHub/Bitbucket/GitLab and check the Webhooks tab.

For GitHub, the address is https://github.com/ACCOUNT_NAME/PROJECT_NAME/settings/hooks.

Look for the webhook that was supposed to reach Buddy and check its status if it successfully reached our service. If everything looks fine, please contact us at support@buddy.works.

  1. If the webhook exists, probably something went wrong while fetching changes to the copy of the repository on Buddy. In this case, go to the Code tab, click Refresh and select the option Clone repository from scratch. If subsequent pushes still do not appear in Activity, please contact us at support@buddy.works.
  2. If the pushes started to appear on the list, but pipelines still aren’t triggered, for 99% the problem are pipelines settings – make sure that the trigger mode is set to On-push trigger in the pipeline settings, the correct ref is selected, and check the trigger conditions in the pipeline. If all these options appear to be correct, please contact us at support@buddy.works.
Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.