Websocket Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID websocket Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
1.0.6 (archives)
Jul 26, 2013
Source Code
Issue Tracking
Open Issues
MIZUNO Hiroki (id: mzp)
Usage Installations 2014-Feb 351
2014-Mar 359
2014-Apr 360
2014-May 354
2014-Jun 339
2014-Jul 374
2014-Aug 364
2014-Sep 387
2014-Oct 388
2014-Nov 379
2014-Dec 369
2015-Jan 374

This plugin notifies build results via Websocket.


  • Notify build result via Websocket
  • If you use modern web browser (e.g. Chrome, Firefox, Safari), you receive realtime build result by Javascript. It includes iPhone/iPad.
  • Offcourse, websocket is independent from browser. You could your favorite laungage to receive realtime build result.


At Manege Jenkins > Configure System > Websocket Notifier, you could configure websocket port.

At (your project) > Configure > Post build Actions, you could enable websokcet notification.

Usage Example

Chrome Extension

Jenkins Notifier for Chrome supports websocket. So you could receive a notification in realtime.

iPad/iPhone as XFD

If you upload https://github.com/jenkinsci/websocket-plugin/blob/master/xfd.html at same host as jenkins, you could use iPhone/iPad as XFD.

Windows client


Version History

Version 1.0.6 (26 July, 2013)

  • Added: "Enable Websocket pings to keep connections alive" option
  • Added: "Use status format" option
  • Updated: webbit version (0.4.7 -> 0.4.15)

Version 1.0.4 (16 April, 2012)

  • Fixed: configurations were not loaded
  • Updated: webbit version (0.3.0 -> 0.4.7)

Version 1.0 (6 June, 2011)

  • Initial release


plugin-notifier plugin-notifier Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 27, 2011

    Chris Hilton says:

    The issue tracking link doesn't seem to work, so I'm just going to add a comment...

    The issue tracking link doesn't seem to work, so I'm just going to add a comment here. The plugin tries to open a port on 8081 by default, but this port is already in use on our server. That prevents Jenkins from starting up at all, so you can't change the configuration to a different port. Failing to open up the port should probably not hang Jenkins, but I would settle for a snippet of configuration that I could use to set the port number.

  2. Sep 12, 2011

    Mike Rudiger says:

    First, thank you for the handy plugin :) I wanted to point that that it appears...

    First, thank you for the handy plugin :)

    I wanted to point that that it appears that after setting the Websocket port under Manage Jenkins --> Configure System, the Port set there is not persisted after a Jenkins restart. This

    is of course not very practical ;) Be nice to have that fixed.