[Gluster-Maintainers] Automatic triggering broken on Jenkins
kshlmster at gmail.com
Sat Nov 21 11:28:21 UTC 2015
On Sat, Nov 21, 2015 at 4:45 PM, Kaushal M <kshlmster at gmail.com> wrote:
> On Fri, Nov 20, 2015 at 10:13 PM, Vijay Bellur <vbellur at redhat.com> wrote:
>> ----- Original Message -----
>>> From: "Kaushal M" <kshlmster at gmail.com>
>>> To: "Niels de Vos" <ndevos at redhat.com>
>>> Cc: maintainers at gluster.org
>>> Sent: Thursday, November 19, 2015 6:14:59 AM
>>> Subject: Re: [Gluster-Maintainers] Automatic triggering broken on Jenkins
>>> On Thu, Nov 19, 2015 at 4:34 PM, Niels de Vos <ndevos at redhat.com> wrote:
>>> > On Thu, Nov 19, 2015 at 03:54:54PM +0530, Kaushal M wrote:
>>> >> The gerrit-trigger plugin which automatically triggered jobs is
>>> >> temporarily not working. We are trying to find out why and will fix it
>>> >> soon.
>> What is the latest on this problem? Has the root cause been established? If not, I can
>> also start looking into this.
> Still no idea why this is broken. The listener which maintains a live
> connection to gerrit for events isn't starting. Except this everything
> else with the gerrit-trigger plugins is working. There is nothing that
> I could find from either of jenkins' or gerrit's logs.
> I want to try restarting Jenkins once, and also want to try updating
> the plugins.
I've updated the plugins and scheduled a restart. Jenkins should
automatically restart after the running jobs finish. We have 2
regression-jobs running which have been going on for ~2 and ~3 hours.
More information about the maintainers