Open Stack

Hi,

We are using the Gearman-plugin<https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin> (version: 0.2.0) at our Nokia's Continuous Integration environment together with Jenkins<https://jenkins.io/index.html> (version: 2.7.1). Except the Gerrit server, the entire CI environment is dockerized: Zuul servers, Jenkins Master instances and build executers being able to scale according the demand. The Gearman is being used to handle multiple Jenkins Master and build executers across the project.

We would like to start docker machines as build executors on demand and according the real CI load. However there seems to be a limitation at the Gearman-plugin (0.2.0), that all available build executors have to be know and running during plugin start-up time. Docker machines started and integrated to Jenkins after plugin start, won't be recognized by the plugin.

We found that is a known issue and documented at: https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin

=== CLIP ===
Known Issues
Adding or removing executors on nodes will require restarting the gearman plugin.  This is because Jenkins does NOT provide provide a way to listen for changes to executors therefore the gearman plugin does not know that it needs to re-register functions due to executor updates.
=== CLIP ===

The Gearman-plugin seems to be still maintained.
Do you know whether that issue has been taken up for next upcoming plugin release?

Thanks in advance for your support.

Best regards.
-----------------------------------------------
Thomas Förster
Manager R&D, A&A Network Management & SON BU
NOKIA

Werinherstr. 91
D-81541 Munich
Germany
Building 5541, Room 3056

Mob:  +49 173-25 57 169
Soft: 8045691

mailto:thomas.foerster at nokia.com
------------------------------------------------

Nokia Solutions and Networks Deutschland GmbH
Geschäftsleitung / Board of Directors: Wichard von Bredow, Birgit Königsheim
Sitz der Gesellschaft: München / Registered office: Munich
Registergericht: München / Commercial registry: Munich, HRB 198136



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20160725/bd5b72da/attachment.html>