When trigged manually the check-merged job
When trigged manually the check-merged job for specific patch we don't see the link in the patch History - see in https://gerrit.ovirt.org/#/c/69802/3 it used to be different .. can we get the link back? Thanks. -- *Yaniv Bronhaim.*
Adding infra-support to open a ticket on it. But it will help if you'll provide example of what you are expecting to see so we'll check its possible. On Mon, Jan 9, 2017 at 11:32 AM, Yaniv Bronheim <ybronhei@redhat.com> wrote:
When trigged manually the check-merged job for specific patch we don't see the link in the patch History - see in https://gerrit.ovirt.org/#/ c/69802/3
it used to be different .. can we get the link back?
Thanks.
-- *Yaniv Bronhaim.*
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
On 9 January 2017 at 11:32, Yaniv Bronheim <ybronhei@redhat.com> wrote:
When trigged manually the check-merged job for specific patch we don't see the link in the patch History - see in https://gerrit.ovirt.org/#/c/69802/3
it used to be different .. can we get the link back?
The replies to Gerrit are done by the Gerrit trigger plugin. Its it is not used to trigger the job, then it also does not (and never did) report to Gerrit. Our Jenkins is configured with complex triggering mechanisms, please avoid triggering jobs manually. If you want to make jobs run , you can emulate Gerrit events with the "Query and Trigger Gerrit patches" screen here: http://jenkins.ovirt.org/gerrit_manual_trigger/ -- Barak Korren bkorren@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/
participants (3)
-
Barak Korren -
Eyal Edri -
Yaniv Bronheim