Nabaztag Plugin

Plugin Information

Allows to publish the result of a build to a Nabaztag.

Configuration

You should access to the configuration page and fill in the Global Nabaztag Settings section:

• Serial Number - The serial number of the device
• Nabaztag API Token - The secret API-Token
• Nabaztag Report On Sucess - report on Sucess - default will be 'false' only failure and recovery will be reported
• Advanced section...
  • Nabaztag API URL - The Nabaztag API URL (that can change among time)
  • Nabaztag Voice - The voice used by the rabbit to spread the build status. A list of supported voices can be found on the API-help page
  • Nabaztag Text for Failure - The text pronounced when build fails
  • Nabaztag Text for Success - The text pronounced when build suceed
  • Nabaztag Text for Recover - The text pronounced when build suceed after a failure

Resources

• http://stephannoske.de/wp/2008/12/hudson-nabaztag-publisher-plugin/ - The plugin original post
• http://www.nabaztag.com - The official Nabaztag web site
• http://api.nabaztag.com - The API documentation page
• http://my.nabaztag.com - Your Nabaztag account
• http://my.violet.net - The Violet account is also able to configure your nabaztag

Changelog

• Release 1.3 (January 08, 2009) >>> nabaztag-1.3.hpi
  • Initial release: (Please do not pay attention to the version. Due to release problems, it is quite unusual. But 1.3 is really the first released version).
• Release 1.4 (January 13, 2009) >>> nabaztag-1.4.hpi
  • Add a new parameter: Report On Success. This would avoid notification of all successfull builds.
  • Using the global Hudson proxy configuration (editable in 'Plugin manager'>'Advanced'>'HTTP proxy') to send notifications.
• Release 1.5 (February 22, 2009) >>> nabaztag-1.5.hpi
  • Fix bug: All Text-To-Speach messages are now editables and supports accentuation.
  • Fix bug: double notification when a build was recovering success.
  • Use a checkbox for the "Report On Success" parameter.
  • Hide non mandatory parameters in an "Advanced..." section.
  • Text-To-Speach messages supports "${projectName}" and "${buildNumber}" special syntax to be more expressive (instead previously of adding project name and build number automatically at the end of the TTS).

Bugs, requests, planned evolutions

Bug	Change	Description	I vote for this !	Fix planned ?	Fixed version
		Need a 'Report On sucess' to be only notified by failures and recovers.		snoske	1.4
		Notification should pass proxy, use global proxy configuration.		Eric Le Merdy	1.4
		'Sucess' and 'Recover' messages are not editable		Eric Le Merdy	1.5
		'Report on sucess' should be a checkbox instead of a true/false text field.		Eric Le Merdy	1.5
		Default serial and token should be blank.		Eric Le Merdy	1.5
		All configuration properties should be set in an 'Advanced...' section except S/N, token and 'report on success'.		Eric Le Merdy	1.5
		Ajax section to test S/N and token validity (is the rabbit exist and is awake ?).
		Text messages should use build variables (e.g. 'Build ${name} has failed.').		Eric Le Merdy	1.5
		My request...