Repository connection issues
If the URL to your repository has suddenly stopped working, jump to this section.
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.
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.
I. Refreshing repository
To refresh the list of commits, go the Code tab in your project and click the Manual fetch button:
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:
- If you find such event on the list, click on it to expand the details:
- If you don't find such event on the list, go to Code ➝ Deliveries and look for failed webhooks:
There can be many types of errors there. The most common reasons the integration doesn’t work are:
- Go to the Integrations tab.
- Click the name of the integration that was used to synchronize the project.
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
Note for GitHub users: If you change the name of the project or move it to a different organization, GitHub updates the project's URL and redirects the old slug to the new address for 30 days. After this time, the old URL stops working on Buddy (we do not receive any information that the URL has changed), which can be confusing for the user given the time between the update on GitHub and the error on Buddy.
- Go to the Code tab.
- Click the hamburger icon at the top.
Switch repository or Git hosting.
- 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:
- If you can’t see any information about new webhooks, refresh the repository manually as in step 1.
- 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
Possible webhook cases
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.
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-pushand correct ref is selected, and check the trigger conditions in the pipeline. If all these options appear to be correct, contact the support team.