Campfire plugin for Hudson
Development of the original plugin seemed to stall, so I forked it to address a number of issues and add some extra features...
- Refactored the code to fix a number of null pointer exceptions.
- Moved from per-job to global config.
- Fixed issues with configuration details being lost after a hudson restart.
- Tidied up jelly view for configuration form and added help files for each field.
- Added a link to the build in notifications sent to campfire.
Thanks to Joshua Krall, we now have support for SSL, and the plugin works after upgrading to Hudson ver. 1.363
Note: I don't have a lot of Java experience, so my code is probably pretty shoddy, but we've been using it for months without any trouble.
You'll need to have JDK 6 and maven2 installed to build the plugin. On OSX with macports this is as simple as...
sudo port install maven2
Then clone the repository and build the package
git clone git://github.com/jgp/hudson_campfire_plugin.git cd hudson_campfire_plugin mvn package
When the build has completed, you'll have a .hpi file available which needs to be uploaded to your Hudson installation. If you already have a campfire plugin installed, you need to delete it first, e.g.
rm -rf /var/lib/hudson/plugins/campfire*
Then use the advanced tab of the plugin manager to upload the hpi file. Finally, restart hudson (note: not reload configuration, restart the hudson daemon).
If you run into problems building the plugin with Maven, make sure Maven is finding the right jdk...
run mvn --version and check the output, if it's not finding jdk 6, make sure you have jdk 6 installed and make sure that the current jdk symlink points at version 6. On OSX, check that /System/Library/Frameworks/JavaVM.framework/Versions/1.6 exists and that /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK points to it. If not, remove the CurrentJDK symlink and re-create it, pointing at the 1.6 directory. Other *nix users may run into similar issues, the solution should be the same, just with different paths.
If you get HttpClient or WebClient exceptions, that probably means you've got some configuration setting wrong (while there is some validation of configuration settings, it's far from extensive).