| 89 | | Most of the deployment problems, after initial configuration, are related to deployment script. As the hook script mainly launches the deployment script, it is important complete previous check before troubleshooting SVN hook script. |
| | 89 | ''Most of the deployment problems, after initial configuration, are related to deployment script. As the hook script mainly launches the deployment script, it is important complete previous checks before troubleshooting SVN hook script.'' |
| | 90 | |
| | 91 | Main causes for problems with hook script are invalid SSH keys for communication with Quattor server and invalid configuration for the hook script. Follow the following steps to identify the problem : |
| | 92 | |
| | 93 | 1. Log on Subversion server as the same user as your Subversion server (generally Apache account). |
| | 94 | 1. Try to ssh to Quattor server as the user used to run deployment script (generally root). |
| | 95 | 1. Retrieve the repository revision where the last tag was created. If the tag has been successfully deployed, the easiest is to use `svn log --limit 1` in SVN cache directory on Quattor server. Else, you need to identify the last tag created in repository with `svn ls` and run `svn log --limit 1` on the corresponding URL. |
| | 96 | 1. Go to the `hooks` directory of Subversion SCDB repository and run the following command (`REPOSITORY_PATH` is the filesystem path to repository) : |
| | 97 | {{{ |
| | 98 | ./post-commit REPOSITY_PATH REVISION |
| | 99 | }}} |
