@Oved Ourfali this was already resolved, please see previous comments.

Adding Eyal.

Thanks,
Oved

On Thu, Nov 10, 2016 at 9:27 PM, Scott Dickerson <sdickers@redhat.com>
wrote:

> Hi,
>
> I submitted an ovirt-engine-dashboard patch [1] last night. The
> gerrit-hooks ran just fine to attach the patch to its BZ [2]. However, the
> normal Jenkins CI hooks/job did not. I tried rerunning the hooks with the
> "Rerun-Hooks: all" gerrit comments on the patch, but Jenkins CI did not run
> again. How can we tell if the Jenkins CI triggers on the
> ovirt-engine-dashboard gerrit are still configured correctly? What can be
> done to fix the problem?
>
> To attempt to work around the issue, I tried the gerrit manual trigger
> page [3]. Unfortunately my jenkins account (sdickers) does not have the
> appropriate permission to the page. My teammate was able to manually
> trigger the job and my patch cleared CI (thanks Greg). Who do I need to
> ping to get that permission added to my account?
>
> Regards,
> Scott
>
> [1] - https://gerrit.ovirt.org/66368
> [2] - https://bugzilla.redhat.com/1389382
> [3] - http://jenkins.ovirt.org/gerrit_manual_trigger/
>
> –
> Scott Dickerson
> Senior Software Engineer
> RHEV-M Engineering - UX Team
> Red Hat, Inc
>

I just pushed a new update on the patch. Jenkins CI started up the builds at the same time as the gerrit-hooks.

Hopefully you did something to make it start working. Otherwise, I'll give credit to the moon phase in relationship to solar flare activity.

^ what he said.

"Manually triggered by user gshereme for Gerrit: https://gerrit.ovirt.org/66368"

Those 2 were triggered manually by @Greg Sheremeta. On that patch at 11:39AM (or equivalent in your timezone), I triggered the hooks. You can see the BZ update task run, but not the typical Jenkins CI.

Patch 65925 [1], that submitted on Oct 31, shows the Jenkins CI tasks at the same time as the BZ updating one.

[1] - https://gerrit.ovirt.org/#/c/65925/