[OpenStack-Infra] [third-party] Fail to use Jenkins+JClouds+Zuul+Gearman for CI systems

Monty Taylor mordred at inaugust.com
Mon Jul 14 16:09:09 UTC 2014


On 07/14/2014 04:40 AM, Lucas Eznarriaga wrote:
> Hi,
> 
> I am trying to use JClouds Jenkins Plugin + Zuul to deploy slaves on demand
> to run the third-party jobs. Using Gerrit trigger plugin, JClouds works
> perfectly, however, it does not work when using Zuul+Gearman because
> Gearman does not register a job assigned to a node label which does not
> exist yet (because it will be created by JClouds when the job is
> triggered).
> The only way to get the job registered in Gearman is not specifying a node
> label.
> However, in this case, the job runs on the master jenkins node and JClouds
> creates a slave which does not run the intended job.
> 
> Has anybody else run into the same issue? Is there any workaround to make
> that work?

We wrote nodepool largely as a result of not being able to get the
jclouds plugin to a usable state for this use case.

If you've moved from gerrt trigger plugin to zuul, I recommend going
ahead and using nodepool for node management.

> Here is a sample of my job configuration:
> 
> - job-template:
>     name: 'noop-check-communication'
>     node: 'third-party'
> 
>     builders:
>       - shell: |
>           #!/bin/bash -xe
>           echo "Hello world, this is the {vendor} Testing System"
> 
> 
>     wrappers:
>       - jclouds:
>           single-use: True
>           instances:
>             - 'cloud-third-party-testing':
>                 cloud-name: my-cloud
>                 count: 1
>                 stop-on-terminate: True
> 
> 
> Thanks,
> Lucas
> 
> 
> 
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 




More information about the OpenStack-Infra mailing list