[
https://ovirt-jira.atlassian.net/browse/OVIRT-824?page=com.atlassian.jira...
]
Scott Dickerson commented on OVIRT-824:
---------------------------------------
Those 2 were triggered manually by [~gshereme(a)redhat.com]. 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/
Jenkins CI not triggering for ovirt-engine-dashboard gerrit patches
-------------------------------------------------------------------
Key: OVIRT-824
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-824
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Scott Dickerson
Assignee: infra
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
--
This message was sent by Atlassian JIRA
(v1000.526.2#100018)