search

matt-richardson / gocd-websocket-notifier

GoCD plugin to publish build notifications via websockets to any listener
11 stars 7 forks source link

How to test websocket connection #13

Closed anjana83 closed 7 years ago

anjana83 commented 7 years ago

Hi,

Can you please help me here: I see this logs once I build pipeline in go-server. Go server is in linux box.

2017-01-18 21:14:08,419 INFO [Thread-70] GoNotificationPlugin:52 - Starting WebSocket server started on port: 8887 2017-01-18 21:14:08,506 INFO [Thread-70] GoNotificationPlugin:52 - WebSocket server started on port: 8887 2017-01-18 21:15:27,930 INFO [69@MessageListener for PluginNotificationListener] WebSocketPipelineListener:52 - notify called with request name 'stage-status' and requestBody '{"pipeline":{"name":"hsd-qa-auto","counter":"32","group":"hsd-services-rs","build-cause":[{"material":{"pipeline-configuration":{"pipeline-name":"hsd-commit","stage-name":"build"},............................

Can you please let me know how can I test that message has sent over websocket.

thanks so much.

matt-richardson commented 7 years ago

You can use http://www.websocket.org/echo.html to test out the messages. It all runs client side so it will be able to access your go server.

anjana83 commented 7 years ago

thanks so much... got it..