Last week we upgraded our Jenkins instance to version 2.46.3 (on/around 05/25/2017). Upon successfully completing/testing that upgrade, we upgraded our Gerrit trigger plug-in version from 2.23.0 -> 2.23.2.
Since performing that Gerrit trigger plug-in upgrade, our Jenkins server has completely stopped processing ANY of the stream events generated by code pushes by our users, period. I've pushed code a number of times myself and the Gerrit trigger plug-in simply ignores all of the events, and this is in spite of the fact that I am monitoring the events coming across myself (in a separate window).
Our configuration is simple; we are not filtering-out any specific event types. This software simply isn't working.
The only way to get things working again was to back-out the 2.23.2 version of the Gerrit trigger plug-in and go back to the 2.23.0 version. Once we bounced the Jenkins server and re-pushed some of the previously-failed changes, everything started working again like clockwork.
Please let me know if there is any additional information I can provide you to help troubleshoot this. We don't have access to the log files on our Gerrit servers (it's centralized in a datacenter in France), but I do have access to our Jenkins server's logs.
I will assist you in any way I can.
I created this tracker as 'Major' because I believe it deserves investigation and prior to the creation of this tracker – literally only an hour ago – it was blocking our ability to deliver our product. I consider the fallback to 2.23.0 to be a fortunate work-around, but it's not optimal. We like to keep our plug-ins updated with the latest versions whenever possible.
Any help you can offer is greatly appreciated!
Marcus E. Harris