[OpenStack-Infra] [openstack-dev] [cinder] How to configure the third party CI to be triggered only when jenkins +1

John Griffith john.griffith8 at gmail.com
Tue Feb 23 01:40:13 UTC 2016


On Mon, Feb 22, 2016 at 6:32 PM, liuxinguo <liuxinguo at huawei.com> 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 the third party CI to
> be triggered only when jenkins +1?
>
>
>
> Thanks for any input!
>
>
>
> Regards,
>
> Wilson Liu
>
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> ​In my case I inspect the comments and only trigger a run on either "run
solidfire" or on a Jenkins +1.  The trick is to parse out the comments and
look for the conditions that you are interested in.  The code looks
something like this:

if (event.get('type', 'nill') == 'comment-added' and

'Verified+1' in event['comment'] and
cfg['AccountInfo']['project_name'] == event['change']['project'] and
event['author']['username'] == 'jenkins' and
event['change']['branch'] == 'master'):
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20160222/604bb0e2/attachment.html>


More information about the OpenStack-Infra mailing list