Web hook push events not working

Web hook push events seems to live their own life. Sometimes they work and sometimes they don't. When it decides to not work seems to be quite random. This is quite annoying.

See #3150 (closed) for more info, that issue is over 8 months old and no updates.

Added webhooks label

Having the same issue since upgrading from GitLab 8.1. Web hooks work when triggered manually for testing purposes (although I am not sure what exactly is sent when doing the test since my Jenkins instance thinks the master branch got updated..).

However when doing a push while the web hook is configured to listen to "Push events" does nothing.

Here is the tail of gitlab-rails/production.log when doing a push:

Started GET "/web/thebackend.git/info/refs?service=git-receive-pack" for 92.203.132.60 at 2016-08-10 22:53:17 +0200
Processing by Projects::GitHttpController#info_refs as */*
  Parameters: {"service"=>"git-receive-pack", "namespace_id"=>"web", "project_id"=>"thebackend.git"}
Completed 200 OK in 46ms (Views: 0.3ms | ActiveRecord: 4.5ms)
Started POST "/web/thebackend.git/git-receive-pack" for 92.203.132.60 at 2016-08-10 22:53:17 +0200
Processing by Projects::GitHttpController#git_receive_pack as application/x-git-receive-pack-result
  Parameters: {"namespace_id"=>"web", "project_id"=>"thebackend.git"}
Completed 200 OK in 79ms (Views: 0.3ms | ActiveRecord: 8.9ms)
Started POST "/api/v3/internal/allowed" for 127.0.0.1 at 2016-08-10 22:53:17 +0200
Started GET "/api/v3/internal/broadcast_message" for 127.0.0.1 at 2016-08-10 22:53:18 +0200

This is the respective output in the same log file when doing the manual test of the same web hook:

Started GET "/web/TheBackend/hooks/7/test" for 92.203.132.60 at 2016-08-10 22:56:07 +0200
Processing by Projects::HooksController#test as HTML
  Parameters: {"namespace_id"=>"web", "project_id"=>"TheBackend", "id"=>"7"}
Redirected to https://git.lrx-solutions.de/web/TheBackend/hooks
Completed 302 Found in 234ms (ActiveRecord: 9.4ms)
Started GET "/web/TheBackend/hooks" for 92.203.132.60 at 2016-08-10 22:56:07 +0200
Processing by Projects::HooksController#index as HTML
  Parameters: {"namespace_id"=>"web", "project_id"=>"TheBackend"}
Completed 200 OK in 223ms (Views: 90.8ms | ActiveRecord: 17.8ms)
Started GET "/web/TheBackend/autocomplete_sources" for 92.203.132.60 at 2016-08-10 22:56:09 +0200
Processing by ProjectsController#autocomplete_sources as JSON
  Parameters: {"namespace_id"=>"web", "id"=>"TheBackend"}
Completed 200 OK in 335ms (Views: 119.9ms | ActiveRecord: 22.3ms)

As I said, the manual test produces a request on the other end (in my cases a Jenkins instance) while the push event does not.

moved to gitlab#5217

Hey! 👋

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue