Troubleshoot

If you need further assistance setting up GitOps, feel free to reach us.

General

  1. Bytebase only observes merge event. If the file is pushed to the branch directly, it will be ignored.
  2. Migration file must follow the path and naming convention.
  3. Bytebase has configured a proper External URL and the URL is network accessible from VCS.

Bytebase observes the VCS merge event via webhook. The created webhook link is on the top of the Git connector setting page.

webhook-link

Check the webhook running history to debug the reason.

webhook-running-detail

GitLab

Failed to create webhook xxx, status code: 422

If you configure External URL with the private IP such as 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, you will need to enable Allow requests to the local network from webhooks and integrations first.

activity-warning

INVALID_ARGUMENT: failed to fetch repositories

gitlab-invalid-pat

If your GitLab is before 12.2, then the personal access token won't work and you need to use the OAuth token to configure the GitLab Provider

Edit this page on GitHub

Subscribe to Newsletter

By subscribing, you agree with Bytebase's Terms of Service and Privacy Policy.