-
Bug
-
Resolution: Won't Fix
-
Critical
-
None
After gitea update (version 1.14.0+dev-707-g66a148e39) pipelines for multiple branches/commits don't work at all (hooks are being sent though): commit doesnt'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.
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.
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.
[JENKINS-64920] Hooks partly don't work after gitea update
Anton
added a comment - How can we initiate progress in this task? bug is quite significant cause we don't have pipelines for master branch now.
Anton
added a comment - How can we initiate progress in this task? bug is quite significant cause we don't have pipelines for master branch now. Hi lakostin,
As you can see in https://github.com/jenkinsci/gitea-plugin, there is no activity since august from the maintainer(s), and because of this I don't have too much enthusiasm to look around about the issue.
If you can reach stephenc, maybe he can help you and others to start again the development around the plugin.
If I see any maintainer activity around the plugin, then I will have a look about this issue. 
Daniel Mecsei
added a comment - - edited Hi lakostin ,
As you can see in https://github.com/jenkinsci/gitea-plugin , there is no activity since august from the maintainer(s), and because of this I don't have too much enthusiasm to look around about the issue.
If you can reach stephenc , maybe he can help you and others to start again the development around the plugin.
If I see any maintainer activity around the plugin, then I will have a look about this issue. Anton
added a comment - stephenc , can you have a look at this? Hi.
I just ran into this bug as well, although the issue even appears in versions as low as 1.13.2 (and possibly even lower).
Right now I can work around the issue by adding a crude rewrite rule to nginx that appends ?limit=100 to the URL when /api/v1/user/repos is matched:
rewrite ^(.*\/api\/v1\/users\/\w+\/repos)$ $1?limit=100;
Without it, it seems to be limited to 15 repos.
Anton
added a comment - nekusoul, there is an easier solution - to change api numbers:
https://github.com/go-gitea/gitea/blob/master/custom/conf/app.example.ini#L1158-L1160
Anton
added a comment - nekusoul , there is an easier solution - to change api numbers:
https://github.com/go-gitea/gitea/blob/master/custom/conf/app.example.ini#L1158-L1160
I have some problem too. Do you have a solution to this problem?