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.

If you encounter this problem for the first time, in 9 out of 10 cases refreshing the repository on Buddy will help (see below).

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

Possible solutions

I. Refreshing repository

To refresh the list of commits, go the Code tab in your project and click the Manual fetch button:

Fetching missing commitsFetching missing commits

Checking provider status

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

II. Re-adding desynchronized project

If you don’t see the Deliveries tab in your code details, it means that somebody in the workspace has changed the Git provider to Buddy, i.e. 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.

III. Debugging connection events

If refreshing the repository manually no longer helps, and you are sure your Git provider is up and running, select Activity from the left navigation panel 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:

Expired token

  1. Go to the Integrations tab.
  2. Click the name of the integration that was used to synchronize the project.
  3. Click Refresh OAuth token.

No access to the project or limited rights

This means that the user who added the integration no longer has access rights to the project hosted on the selected Git provider

Project name/URL has changed

  1. Go to the Code tab.
  2. Click the hamburger icon at the top.
  3. Select Switch repository or Git hosting.
  4. Adjust the configuration and click Switch repository.

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

IV. 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 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 > Deliveries and check the webhooks:

  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's options on your Git provider and look up the Webhooks tab. Locate the webhook that was supposed to reach Buddy and check its status to see if it did reach our service. If everything looks fine, contact our support team.

In GitHub, the webhooks are located at https://github.com/ACCOUNT_NAME/PROJECT_NAME/settings/hooks.

Possible webhook cases

  1. If the webhook does exist, probably something went wrong while fetching changes to the copy of the repository on Buddy.

    Solution: Fetch the commits manually as in step 1 but make sure to select the option Clone repository from scratch. If subsequent pushes still do not appear on the activity stream, contact the support team.

  2. If pushes started to appear in Buddy but pipelines still aren’t triggered, for 99% the problem are pipelines settings.

    Solution: Make sure that the pipeline's trigger mode is set to On-push and correct ref is selected, and check the trigger conditions in the pipeline. If all these options appear to be correct, contact the support team.