- 新しい順
- 投票が多い順
- コメントが多い順
The issue you're experiencing with your CodeBuild-hosted GitLab runner webhook failing with the error "Invalid Webhook request received: Missing source repository" could be due to several factors, but it's not likely related to your GitLab version being too old.
GitLab Community Edition 15.11.6 should be compatible with CodeBuild-hosted GitLab runners. The error suggests that there might be an issue with how the webhook is configured or how the repository information is being passed to CodeBuild.
Here are some troubleshooting steps you can try:
- Check the webhook settings in GitLab:
- Verify that the webhook is properly enabled and configured to deliver the appropriate events, particularly the Workflow jobs events.
- Review recent webhook deliveries in GitLab to see if there are specific error messages or response codes.
- Verify your CodeBuild project configuration:
- Ensure that your CodeBuild project name in AWS matches exactly what you've specified in your .gitlab-ci.yml file.
- Check that the tags section in your gitlab-ci.yml correctly points to your CodeBuild runner.
- Check webhook event filter groups:
- Confirm that you have set the event type to WORKFLOW_JOB_QUEUED in your CodeBuild configuration.
- Examine network connectivity:
- Ensure there are no network issues preventing GitLab from reaching your AWS CodeBuild endpoint.
- Check if any network configurations or firewall rules might be blocking the connection.
- Review permissions:
- Verify that CodeBuild has sufficient permissions to access your GitLab repository.
- Check if your CodeBuild project's IAM role has the necessary permissions.
If the webhook continues to fail, you might need to manually re-enable it after addressing the underlying issues, as GitLab automatically disables webhooks after multiple failed attempts.
Sources
CodeBuild-hosted GitLab runner: webhook Failed to connect | AWS re:Post
Troubleshoot the webhook permission issues - AWS CodeBuild
