...@gmail.com]
发送时间: 2016年2月23日 20:35
收件人: OpenStack Development Mailing List (not for usage questions)
抄送: OpenStack Infra; Luozhen
主题: Re: [OpenStack-Infra] [openstack-dev] [cinder] How to configure the third
party CI to be triggered only when jenkins +1
On Mon, Feb 22, 2016 at 7:32 PM, liuxinguo
On Mon, Feb 22, 2016 at 7:32 PM, liuxinguo wrote:
> Hi,
>
>
>
> There is no need to trigger third party CI if a patch does not pass Jenkins
> Verify.
>
> I think there is a way to reach this but I’m not sure how.
>
>
>
> So is there any reference or suggestion to configure
送时间: 2016年2月23日 9:40
> 收件人: OpenStack Development Mailing List (not for usage questions)
> 抄送: OpenStack Infra; Luozhen
> 主题: Re: [OpenStack-Infra] [openstack-dev] [cinder] How to configure the third
> party CI to be triggered only when jenkins +1
>
>
>
> On Mon
Development Mailing List (not for usage questions)
抄送: OpenStack Infra; Luozhen
主题: Re: [OpenStack-Infra] [openstack-dev] [cinder] How to configure the third
party CI to be triggered only when jenkins +1
On Mon, Feb 22, 2016 at 6:32 PM, liuxinguo
<liuxin...@huawei.com<mailto:liuxin...@huaw
On Mon, Feb 22, 2016 at 6:32 PM, liuxinguo wrote:
> Hi,
>
>
>
> There is no need to trigger third party CI if a patch does not pass
> Jenkins Verify.
>
> I think there is a way to reach this but I’m not sure how.
>
>
>
> So is there any reference or suggestion to configure
Hi,
There is no need to trigger third party CI if a patch does not pass Jenkins
Verify.
I think there is a way to reach this but I'm not sure how.
So is there any reference or suggestion to configure the third party CI to be
triggered only when jenkins +1?
Thanks for any input!
Regards,