my fix didn't seem to "stick" and didn't work when Adar tried it again later.
Restarting jenkins entirely seems to unstick it for a bit. I enabled debug logging for the gerrit trigger, hopefully that will tell us something useful when it gets stuck again. Meanwhile committers can trigger builds using http://jenkins.kudu.apache.org/gerrit_manual_trigger/ (seems to work fine even when the automatic trigger gets stuck) -Todd On Thu, Jun 29, 2017 at 11:22 AM, Todd Lipcon <t...@cloudera.com> wrote: > For some reason Jenkins stopped auto-triggering builds last night. Not > sure exactly what happened, but I think I've kicked it into working again. > > For future reference, the thing I did to kick it was to navigate to > http://jenkins.kudu.apache.org/gerrit-trigger/ and click the little blue > orb under the "Status" column. On the first click it went red, and then I > clicked it again and it went blue again. > > I also chanted some Latin and sacrificed a chicken while I clicked on the > orb. Not sure which of my actions did the trick, but I just uploaded a new > patch to gerrit and Jenkins did its thing. > > -Todd > -- > Todd Lipcon > Software Engineer, Cloudera > -- Todd Lipcon Software Engineer, Cloudera
