[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Ferruccio Bongianni commented on JENKINS-56528 Re: Gerrit trigger 2.29.0 does not trigger jobs Hi, is there any progress on this? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198136.1552412561000.6108.1578646500232%40Atlassian.JIRA.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Georg Bremer commented on 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 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198136.1552412561000.1247.1571990340616%40Atlassian.JIRA.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Georg Bremer started work on JENKINS-56528 Change By: Georg Bremer Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198136.1552412561000.1231.1571990285037%40Atlassian.JIRA.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Georg Bremer updated JENKINS-56528 Jenkins / JENKINS-56528 Gerrit trigger 2.29.0 does not trigger jobs Change By: Georg Bremer Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198136.1552412561000.1239.1571990285847%40Atlassian.JIRA.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Georg Bremer assigned an issue to Georg Bremer Jenkins / JENKINS-56528 Gerrit trigger 2.29.0 does not trigger jobs Change By: Georg Bremer Assignee: rsandell Georg Bremer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198136.1552412561000.1217.1571990283066%40Atlassian.JIRA.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title
Georg Bremer updated an issue
Jenkins / JENKINS-56528
Gerrit trigger 2.29.0 does not trigger jobs
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 checkQueueSizeWARNING: 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.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title S. Panchenko commented on JENKINS-56528 Re: Gerrit trigger 2.29.0 does not trigger jobs 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Torben Thellefsen commented on JENKINS-56528 Re: Gerrit trigger 2.29.0 does not trigger jobs 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Max P commented on 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Torben Thellefsen created an issue Jenkins / JENKINS-56528 Gerrit trigger 2.29.0 does not trigger jobs Issue Type: 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 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
