Last modified: 2014-10-24 13:46:40 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65758, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63758 - [upstream] Jenkins: jobs created via JJB are not properly registered in Zuul Gearman server
[upstream] Jenkins: jobs created via JJB are not properly registered in Zuul ...
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: High normal (vote)
: ---
Assigned To: Antoine "hashar" Musso (WMF)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-10 07:49 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-10-24 13:46 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2014-04-10 07:49:00 UTC
When creating new jobs using Jenkins Job Builder, the job ends up not being registered in the Zuul Gearman Server.  That causes jobs to never be find and report an error such as:

 https://integration.wikimedia.org/ci/job/mwext-TextExtracts-jslint/None/console : LOST

In Zuul /var/log/zuul/debug.log we have:

 2014-04-10 07:41:38,332 DEBUG zuul.Gearman: Function build:mwext-TextExtracts-jslint is not registered


Querying the Gearman server:

 $ echo status|nc -q 3 localhost 4730|grep  TextExtracts
 $


The Jenkins debug log does not show any event related to TextExtracts.  It seems the Gearman plugin does not trigger jobs registration when jobs are created via Jenkins REST API.


Workaround: use the web GUI to save any job and that triggers the registration of any missing jobs.
Comment 1 Antoine "hashar" Musso (WMF) 2014-08-19 14:46:10 UTC
Reported upstream as https://bugs.launchpad.net/gearman-plugin/+bug/1353891

That is an issue in Jenkins Gearman Plugin which might not work properly with the latest Jenkins LTS version we are using.
Comment 2 Antoine "hashar" Musso (WMF) 2014-08-19 14:49:41 UTC
I am tracking this with upstream on launchpad.  Not much I can do beside giving them traces / informations.
Comment 3 Antoine "hashar" Musso (WMF) 2014-10-09 08:12:33 UTC
I managed to describe how to reproduce the issue and confirmed it. Upstream author Khai Do happily followed up with a code update which is being proposed on https://review.openstack.org/125755

The root cause is a change in Jenkins core events a plugin can listen to.
Comment 4 Antoine "hashar" Musso (WMF) 2014-10-14 12:41:21 UTC
I have upgraded Jenkins Gearman plugin to fix jobs registrations:
* cherry picked https://review.openstack.org/#/c/125755/ patchset 8
* compiled it via maven
* uploaded and restarted Jenkins

The job do register.

I am keeping this bug opened while upstream patch is polished.
Comment 5 Antoine "hashar" Musso (WMF) 2014-10-21 16:18:04 UTC
Upstream patch has been merged and applied on our setup.  Need to verify whether the gearman plugin has been actually released and switch to that version (should be 0.8).
Comment 6 Antoine "hashar" Musso (WMF) 2014-10-24 13:46:40 UTC
The plugin has been released and is applied on our Jenkins.  Jobs created via JJB are now properly registered with Zuul Gearman server upon creation.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links