Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Re: When trigged manually the check-merged job

Description

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)

Activity

Show:

Eyal Edri July 3, 2017 at 2:22 PM

please reopen if you see it again and provide details.

Barak Korren February 27, 2017 at 12:05 PM

It doesn't make sense this ever worked. The thing that adds the Gerrit comments is the Gerrit trigger.
If you're triggering manually you're not using it (unless you emulate triggering using this page).

Former user February 27, 2017 at 11:55 AM

once I trigger manually using jenkins check_merged vdsm job, the job starts
as expected, but the link to that job does not appear in the gerrit patch
page. In the past we used to to have new comment in the patch page about
manual triggering

On Sun, Feb 26, 2017 at 4:00 PM, eyal edri [Administrator] (oVirt JIRA) <

–
Yaniv Bronhaim.

Eyal Edri February 26, 2017 at 2:00 PM

can you link an example and the reasoning behind this?

check-merged are running on HEAD, not open patches as check-patch

Cannot Reproduce

Details

Assignee

Reporter

Priority

Parent

Created January 9, 2017 at 10:47 AM
Updated August 3, 2017 at 3:02 PM
Resolved July 3, 2017 at 2:22 PM