Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webhooks on mirrored repositories broken #5441

Closed
2 of 7 tasks
serverwentdown opened this issue Dec 1, 2018 · 9 comments · Fixed by #7366
Closed
2 of 7 tasks

Webhooks on mirrored repositories broken #5441

serverwentdown opened this issue Dec 1, 2018 · 9 comments · Fixed by #7366
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug

Comments

@serverwentdown
Copy link
Contributor

serverwentdown commented Dec 1, 2018

  • Gitea version (or commit ref): bc42b3a
  • Git version: 2.18.1
  • Operating system: Docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (try.gitea.io won't sync the mirror)
    • Not relevant
  • Log gist:

Description

Gitea synchronizes mirrors but triggering the webhooks fails with no error and the webhook does not get called, contuary to #4127. Pressing "Test Delivery" however, triggers the webhook successfully and causes previous failed webhooks to succeed.

Screenshots

@stormmore
Copy link

stormmore commented Dec 3, 2018

I am also facing this issue and I am using a PG backed instance. I have found that restarting Gitea has the resulting effect of sending the "missed" deliveries!

(Edit: FYI my instance's commit is 0da8bc9)

@stormmore
Copy link

This is also happening on commit ad9f9cd and to confirm only for events that come in from the mirrors being synced.

I have an Org level webhook that works properly for other repos that are not mirrors.

@ericsgagnon
Copy link

still an issue on v1.7 release - commit 41a2bfe, docker image deployment with PG backend. Mirroring from a gitlab repo.

@stefanak-michal
Copy link

stefanak-michal commented Jan 16, 2019

Hi.
I've same problem. I have webhook for create/delete repository in organization. Its working only for delete repository.

  • Gitea version (or commit ref): 1.7 (41a2bfe)
  • Git version: 2.18.0
  • Operating system: CentOS 7
  • Database (use [x]):
    • PostgreSQL
    • MySQL (MariaDB 15.1)
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (It's running on private network)
    • Not relevant
  • Log gist:

vystrizek

I created webhook for it, because new created repository is not automatically assigned to all teams of owner organization. I'm just doing few API request with webhook target php script. If there is another option how to achieve it, I'll be glad for response.

@LeKovr
Copy link

LeKovr commented Jan 21, 2019

Same problem. Also when I press "Test delivery" after mirroring, gitea raises several hooks simultaneously - one for every push at mirror + testing

@tgly307
Copy link

tgly307 commented Jan 22, 2019

Same problem in 1.6.2 release.

@stefanak-michal
Copy link

One more information, I have this problem with normal repositories, not mirror.

@ryan-harper-dentsu
Copy link

same issue her for me as @stefanak-michal . Delete works but not the create for a repository.

@stale
Copy link

stale bot commented May 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label May 12, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label May 12, 2019
@stale stale bot removed the issue/stale label May 12, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants