sameersbn / sameersbn/docker-gitlab

Webhooks don't trigger

Open
#447 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Hi,

If someone could help me, I certainly miss some conf...

I have a Gitlab container running (thanks !), all features working, but there is only one weird thing with webhook :

  • when I hit Test webhook, it works
  • when I push from my local repo to the gitlab remote repo, webhooks don't trigger anything

I use git bash for windows (maybe ?), and I've tested with requestb.in and my own script.
Gitlab container is started with docker-compose, and Web UI is behind an apache2 proxy.
I can't figure what I'm doing wrong.

Is there any specific configuration or workflow ?

Thanks in advance ! And thanks yet for the work !

PS : my docker-compose.yml (some private vars are replaced of course)

data:
  image: busybox
  volumes:
    - ---:/var/lib/postgresql
    - ---:/var/lib/redis
    - ---:/home/git/data
    - ---:/home/git/gitlab-shell/hooks
dbpg:
  image: sameersbn/postgresql:latest
  environment:
    - DB_NAME=gitlabhq_production
    - DB_USER=gitlab
    - DB_PASS=---
  volumes_from:
    - data
redis:
  image: sameersbn/redis:latest
  volumes_from:
    - data
gitlab:
  image: sameersbn/gitlab:8.0.2
  environment:
    - TZ=Europe/Paris
    - GITLAB_HOST=---
    - GITLAB_EMAIL=---
    - GITLAB_EMAIL_REPLY_TO=---
    - GITLAB_BACKUPS=daily
    - GITLAB_BACKUP_EXPIRY=1209600
    - GITLAB_PORT=10080
    - GITLAB_SSH_PORT=10022
    - GITLAB_TIMEZONE=Paris
    - GITLAB_SECRETS_DB_KEY_BASE=---
    - SMTP_ENABLED=true
    - SMTP_STARTTLS=true
    - SMTP_TLS=true
    - SMTP_AUTHENTICATION=login
    - SMTP_OPENSSL_VERIFY_MODE=none
         -- all smpt confs (SMTP_PORT....)
  links:
    - dbpg:postgresql
    - redis:redisio
  volumes_from:
    - data
  ports:
    - "10080:80"
    - "10022:22"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the docker-compose.yml configuration and the Apache2 proxy setup described in the issue. Compare the successful Test webhook request with the push-triggered webhook path, using requestb.in or the user's script to observe delivery. Done means identifying the configuration or workflow issue that prevents push webhooks from reaching the endpoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
apache, docker, docker-compose, gitlab
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.