x
/
zmq-event-publisher
Code Issues Proposed changes
RETIRED, Jenkins plugin to publish build events via ZMQ PUB SUB.
13 Commits 1 Branch 5 Tags 172 KiB
Go to file
Clark Boylan df9ee54284 Get master hostname from master computer object. 
Jenkins.getDisplayName() is useless and returns "Jenkins". Get the name
of the master via the Jenkins master computer object. Fall back on
doing a DNS name lookup otherwise.

Change-Id: Icee4e22e9ca989fd1faa6d27f4dad3be76da6385
 		2014-01-29 18:06:10 -08:00
src/main Get master hostname from master computer object. 2014-01-29 18:06:10 -08:00
.gitignore Initial proof of concept for zmq event publisher. 2013-01-23 10:40:09 -08:00
.gitreview add a gitreview file 2013-07-24 15:39:47 -07:00
LICENSE Initial proof of concept for zmq event publisher. 2013-01-23 10:40:09 -08:00
README Use single thread to perform all zmq sends. 2013-01-31 10:59:53 -08:00
pom.xml setup a parameter for the plugin version 2013-07-24 09:03:44 -07:00
run-fast Initial proof of concept for zmq event publisher. 2013-01-23 10:40:09 -08:00

README 

This is a Jenkins plugin that will publish Jenkins Job run events
(start, complete, finish) to a ZMQ PUB socket. By default the PUB
socket is on TCP port 8888 and no Job events will be published.
You can choose to enable event publishing for all jobs in the
Jenkins' global config or enable the plugin on a per job basis.

This plugin uses jeromq to satisfy the dependency on ZMQ. It is
possible to use jzmq instead if you need the features that jeromq
is lacking; however, it is a pain to get jzmq built and is less
portable. If you really really want jzmq look back in the git
history and you will find the old versions of this plugin that
depended on jzmq.

TODO:
- Avoid reading in the global config for each event if possible.
- Need to allow ZMQRunnable thread to die if something truly
  unexpected happens. The RunListener should then start a new
  DaemonThread to handle further events.
- Cleanup config.jelly for the non global Job config.

This plugin borrows heavily from the Jenkins Notification Plugin
https://github.com/jenkinsci/notification-plugin. That plugin
does much of the same work and where applicable I have gone the
easy route and copied the work they have done.