forked from hankman2k/HipChat-SVN-post-commit
-
Notifications
You must be signed in to change notification settings - Fork 0
Using the SVN post-commit hook, sends information to your registered HipChat room (www.hipchat.com)
License
kgleason/HipChat-SVN-post-commit
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
post-commit: Hook used for SVN post commits This script is set to publish information after SVN commits to HipChat. This version is a fork of the project published by hankman2k here: https://github.com/hankman2k/HipChat-SVN-post-commit The original version was designed to work on a Linux SVN Server. A version was needed that would work against a VisualSVN server. The script uses the hipchat_cli to do all the heavy lifting. This is required, unless you want to create/use a different hipchat_cli. Required files/Application/services: * hipchat_room_message: https://github.com/hipchat/hipchat_cli * Visual SVNServer: http://www.visualsvn.com/server/ * Some sort of linux shell that can access your SVN repository * Working repository (you're on your own here) * HipChat account and room setup: https://www.hipchat.com/ * HipChat token created: https://www.hipchat.com/groups/api * PLink.exe on your SVN server * a Putty private key that can connect to your linux shell At a high level, this process will use the post-commit hooks that are built into VisualSVN. This hook will ssh to the shell in question, passing in the name of the repository and the revision number to the post-commit script you find here. The hipchat_cli and post-commit bash script should be located on the same box. The user MUST edit the script file to add in * hipchat token * hipcaht room number * location of hipchat-cli * the name of a user that can read the SVN repository * the password of that user * a user name for display in hipchat * location of temp file. To test: 1) Edit script file 2) chmod 755 script file 3) # ./post-commit <svn repo> <rev #> where <svn repo> is the short name of the repository and <rev #> is any number. The REV number does not have to be accurate. 4) Look at your log in HipChat and verify that information was posted. 5) Finally, add/update a file in your checked out repository and commit. 6) Look at your log in HipChat and verify that information was poster. Note from author: If you like this script and get use out of it, give back! Yep. You too can give something back to the open source communities. If you can give code, give money to your favorite open source program. Keep open source alive.
About
Using the SVN post-commit hook, sends information to your registered HipChat room (www.hipchat.com)
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- Shell 100.0%