Uses HipChat API v2.
What makes it different from other HipChat Jenkins Plugins?
- it works because it uses latest HipChat APIv2 :)
- can specify token created by room owner (no more HipChat admin required!),
- can define token per job (no more global token for all jobs set by Jenkins Administrator!).
If you don't want to compile plugin yourself, feel free to download latest pre-compiled version (pick hipchat-notifier.hpi) and go to uploading instructions.
If you want to compile plugin yourself, follow these steps:
sudo apt-get install openjdk-7-jdk maven2
git clone [email protected]:havramar/hipchat-notifier-plugin.git
cd hipchat-notifier-plugin
mvn package
As a result target/hipchat-notifier.hpi should be created.
To upload it to Jenkins:
- run Jenkins (assuming it will run as http://localhost:8080),
- visit Plugins Manager (advanced)
- pick path to plugin and submit,
- restart Jenkins.
Manage Jenkins -> System Settings -> Hip Chat Notifier (section)
- your api token - https://{xxxx}.hipchat.com/account/api
Job Page -> Configure -> Post-build Action (section) -> Add post-build action
- RoomName or RoomID
- The name or id of the room which to notify
- Auth token
- API Access (personal),
- Room Notification (created by room owner),
- Message Format (SUCCESS)
- Message Format (FAILED)
- Massage from file
- Load notify message from file
- ignore message format setting
- post success notification
- To set whether to notify if the build is successful
- success notification to notify:true
- To set whether to notify parameter of success notification to true
- post failed notification
- To set whether to notify if the build is failed
- failed notification to notify:true
- To set whether to notify parameter of failed notification to true