nday, 30 January 2017 at 13:40
> *To: *Fatih Degirmenci <fatih.degirme...@ericsson.com>, Chigang <
> chig...@huawei.com>, "opnfv-tech-discuss@lists.opnfv.org" <
> opnfv-tech-discuss@lists.opnfv.org>
>
>
> *Subject: *Re: [opnfv-tech-discuss] [Releng/Octopus
with this after Danube.
>
>
>
> /Fatih
>
>
>
> *From: *<opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of Yujun
> Zhang <zhangyujun+...@gmail.com>
> *Date: *Tuesday, 24 January 2017 at 08:41
> *To: *Chigang <chig...@huawei.com>, "op
discuss@lists.opnfv.org"
<opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion
I think it is technically feasible.
We added an experimental trigger for doctor project not long ago[1]. The
trigger is simila
I think it is technically feasible.
We added an experimental trigger for doctor project not long ago[1]. The
trigger is similar to your requirement.
[1]:
https://gerrit.opnfv.org/gerrit/#/c/26839/4/jjb/global/releng-macros.yml
On Tue, Jan 24, 2017 at 12:31 PM Chigang (Justin)
Hi,
The Command "recheck" is used to run default patch verification again in
Gerrit.
But there are so many scenarios to be vericated, I think default patch
verification is not enough.
Is it possible to add a "scenarios" parameters to improve additional
verification before patch merged in
