Not able to trigger build for patch

[Piotr Kliczewski]

Thanks, somehow I missed the fact that it is a draft.

I just forgot to publish it.


On Mon, Nov 9, 2015 at 7:35 PM, David Caro <dcaro at redhat.com> wrote:
>
> Sagi is looking into this, the issue is that we are not triggering on draft
> created, nor draft published nor commit message only changes.
>
> Sagi is adding triggering for draft published event.
>
>
> For this specific patch, there's no way to retrigger (as the gerrit trigger
> patch only supports emulating the patchset created event for now).
>
> There's an open task to add a way on triggering in some other way, but for now
> any of us can force it manually (or a rebase or any code change will also
> retrigger a job).
>
> I've triggered it manually for now [1] but that will not give you any reviews
> in you patch (another shortcoming of the trigger plugin). You might have to
> wait until it starts running for the below page to exist.
>
> [1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/43
>
>
>
> On 11/09, Piotr Kliczewski wrote:
>> The build was never triggered and I am not able to trigger manually a
>> build for [1] patch.
>> Can someone please take a look?
>>
>>
>> [1] https://gerrit.ovirt.org/#/c/47637
>> _______________________________________________
>> Infra mailing list
>> Infra at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>
> Tel.: +420 532 294 605
> Email: dcaro at redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605