[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs

13 views
Skip to first unread message

torbenthellefsen@gmail.com (JIRA)

unread,
Mar 12, 2019, 1:43:03 PM3/12/19
to jenkinsc...@googlegroups.com
Torben Thellefsen created an issue
 
Jenkins / Bug JENKINS-56528
Gerrit trigger 2.29.0 does not trigger jobs
Issue Type: Bug Bug
Assignee: rsandell
Components: gerrit-trigger-plugin
Created: 2019-03-12 17:42
Environment: Linux, openjdk 8, Jenkins 2.150.3, gerrit-trigger 2.29.0, gerrit server runs 2.13.7, lots of other plugins.
Priority: Major Major
Reporter: Torben Thellefsen

After upgrading yesterday, triggering stopped working today. There is some evidence that triggering did work for a time, but not conclusive.

I tried restarting Jenkins, then Gerrit. Nothing helped.

Saw logs of "too many events in the queue" (similar to JENKINS-52636), but the whole setup felt more like JENKINS-53738.

What finally helped was downgrading to 2.28.0 of the plugin. Then triggering started again. I never tried re-saving a job; we have a few too many of those that I want to do that for all of them.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

gentoozoid@gmail.com (JIRA)

unread,
Mar 23, 2019, 9:33:01 AM3/23/19
to jenkinsc...@googlegroups.com
Max P commented on Bug JENKINS-56528
 
Re: Gerrit trigger 2.29.0 does not trigger jobs

Same issue for me,  I think its caused by PR#350. I don't reproduce it on another jenkins instance with same versions of system and plugins. But I was able to collect trace logs from gerrit-plugin for 2.28.0 and incorrect installation of 2.29.0.

torbenthellefsen@gmail.com (JIRA)

unread,
Mar 24, 2019, 6:27:02 PM3/24/19
to jenkinsc...@googlegroups.com

PR#350 is about handling dynamic configuration, and we certainly have that for most of our jobs, so there is that.

I have no data whether our few statically configured jobs would trigger or not; they run much more rarely than the others.

amdokamal@gmail.com (JIRA)

unread,
Mar 28, 2019, 4:05:06 AM3/28/19
to jenkinsc...@googlegroups.com

Confirmed on Jenkins ver. 2.164.1, Gerrit Trigger 2.29.0. We use groovy-pipeline and dynamicTriggerConfiguration:

pipelineTriggers([gerrit(customUrl: '', dynamicTriggerConfiguration: true, gerritProjects: [[branches: [[compareType: 'PLAIN', pattern: '']], compareType: 'PLAIN', disableStrictForbiddenFileVerification: false, pattern: '']], serverName: 'some_server.com', triggerConfigURL: 'http://some_server.com/triggers.txt', triggerOnEvents: [patchsetCreated(excludeDrafts: false, excludeNoCodeChange: false, excludeTrivialRebase: false)])]) 

Re-trigger via +Query and Trigger Gerrit Patche+s doesn't help.

Workaround: downgrading to Gerrit Trigge 2.28.0.

georg.bremer@here.com (JIRA)

unread,
Oct 25, 2019, 3:57:04 AM10/25/19
to jenkinsc...@googlegroups.com
Georg Bremer updated an issue
 
Change By: Georg Bremer
After upgrading yesterday, triggering stopped working today. There is some evidence that triggering did work for a time, but not conclusive.

I tried restarting Jenkins, then Gerrit. Nothing helped.

Saw logs of
"too many

{code:java}
Jul 18, 2018 5:07:57 PM com.sonymobile.tools.gerrit.gerritevents.GerritHandler checkQueueSize
WARNING: The Gerrit incoming
events in the queue " contains 28095 items! Something might be stuck, or your system can't process the commands fast enough. Try to increase the number of receiving worker threads. Current thread-pool size: 30 {code}
(similar to JENKINS-52636), but the whole setup felt more like JENKINS-53738.

What finally helped was downgrading to 2.28.0 of the plugin. Then triggering started again. I never tried re-saving a job; we have a few too many of those that I want to do that for all of them.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

georg.bremer@here.com (JIRA)

unread,
Oct 25, 2019, 3:58:06 AM10/25/19
to jenkinsc...@googlegroups.com
Georg Bremer assigned an issue to Georg Bremer
Change By: Georg Bremer
Assignee: rsandell Georg Bremer

georg.bremer@here.com (JIRA)

unread,
Oct 25, 2019, 3:58:07 AM10/25/19
to jenkinsc...@googlegroups.com
Georg Bremer started work on Bug JENKINS-56528
 
Change By: Georg Bremer
Status: Open In Progress

georg.bremer@here.com (JIRA)

unread,
Oct 25, 2019, 3:58:08 AM10/25/19
to jenkinsc...@googlegroups.com

georg.bremer@here.com (JIRA)

unread,
Oct 25, 2019, 3:59:04 AM10/25/19
to jenkinsc...@googlegroups.com
Georg Bremer commented on Bug JENKINS-56528
 
Re: Gerrit trigger 2.29.0 does not trigger jobs

I don't know if it's supposed to work like that, but since I have the rights I assigned the ticket to me because I have a PR with a fix: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/403

ferruccio.bongianni@gmail.com (JIRA)

unread,
Jan 10, 2020, 3:55:02 AM1/10/20
to jenkinsc...@googlegroups.com

Hi, is there any progress on this?

Thanks

Reply all
Reply to author
Forward
0 new messages