Hooks partly don't work after gitea update #6886

New Issue

GiteaMirror · 2025-11-02T07:10:00-06:00

GiteaMirror commented

2025-11-02 07:10:00 -06:00

Originally created by @lakostin on GitHub (Feb 17, 2021).

Gitea version (or commit ref):
1.14.0+dev-707-g66a148e39
Git version:
2.30.1
Operating system:
docker Alpine Linux v3.13
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
Log gist:

Description

After gitea update pipelines for multiple branches/commits don't work at all (hooks are being sent though): commit doent't start new pipeline, new branches do not appear in jenkins automatically.
For some branches hooks still work.
Looks like gitea has limits for branches, for which hooks work.
We downgraded gitea to version 1.14.0+dev-514-gd2ee1221c and hooks work well again.
...

Screenshots

Originally created by @lakostin on GitHub (Feb 17, 2021). - Gitea version (or commit ref): 1.14.0+dev-707-g66a148e39 - Git version: 2.30.1 - Operating system: docker Alpine Linux v3.13 - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - Log gist: ## Description After gitea update pipelines for multiple branches/commits don't work at all (hooks are being sent though): commit doent't start new pipeline, new branches do not appear in jenkins automatically. For some branches hooks still work. Looks like gitea has limits for branches, for which hooks work. We downgraded gitea to version 1.14.0+dev-514-gd2ee1221c and hooks work well again. ... ## Screenshots ![Screenshot from 2021-02-17 18-53-56](https://user-images.githubusercontent.com/29179059/108230212-8efa7380-7151-11eb-99bc-33b09132075c.png)

GiteaMirror added the issue/needs-feedback label 2025-11-02 07:10:00 -06:00

GiteaMirror closed this issue

2025-11-02 07:10:00 -06:00

GiteaMirror commented

2025-11-02 07:10:01 -06:00

@techknowlogick commented on GitHub (Feb 17, 2021):

We need logs to be able to help you, what do the webhook logs say, what do the standard logs say?

@techknowlogick commented on GitHub (Feb 17, 2021): We need logs to be able to help you, what do the webhook logs say, what do the standard logs say?

GiteaMirror commented

2025-11-02 07:10:01 -06:00

@lakostin commented on GitHub (Feb 18, 2021):

Actually there is nothing interesting in gitea logs, though trace log level is being used.
In project settings i can see that hook was successfully sent and 200 code was returned.
No pipeline started though when i push new branch. But when i create new pull request from this branch, jenkins job starts successfully.
I know it looks like its not a gitea bug but with previous gitea version everything worked well: both branch and pull request hooks started a new job. And we didn't update anything else except gitea. In jenkins logs there are also no errors.

@lakostin commented on GitHub (Feb 18, 2021): Actually there is nothing interesting in gitea logs, though trace log level is being used. In project settings i can see that hook was successfully sent and 200 code was returned. No pipeline started though when i push new branch. But when i create new pull request from this branch, jenkins job starts successfully. I know it looks like its not a gitea bug but with previous gitea version everything worked well: both branch and pull request hooks started a new job. And we didn't update anything else except gitea. In jenkins logs there are also no errors.

GiteaMirror commented

2025-11-02 07:10:01 -06:00

@techknowlogick commented on GitHub (Feb 18, 2021):

I recommend opening up a ticket with the jenkins plugin then. As such I will close this ticket.

@techknowlogick commented on GitHub (Feb 18, 2021): I recommend opening up a ticket with the jenkins plugin then. As such I will close this ticket.

GiteaMirror commented

2025-11-02 07:10:01 -06:00

@lakostin commented on GitHub (Feb 19, 2021):

I recommend opening up a ticket with the jenkins plugin then. As such I will close this ticket.

Do you know how to do it? It's not possible to create an issue without logging in and its not possible to sign up there cause i always get an error))

@lakostin commented on GitHub (Feb 19, 2021): > I recommend opening up a ticket with the jenkins plugin then. As such I will close this ticket. Do you know how to do it? It's not possible to create an issue without logging in and its not possible to sign up there cause i always get an error))

GiteaMirror commented

2025-11-02 07:10:01 -06:00

@techknowlogick commented on GitHub (Feb 19, 2021):

I'm afraid I've never filed a ticket with them, perhaps there is a public email address you can email?

@techknowlogick commented on GitHub (Feb 19, 2021): I'm afraid I've never filed a ticket with them, perhaps there is a public email address you can email?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6886