| | 12 | |
| | 13 | === How do I configure a Windows Slave? === |
| | 14 | * For starters, refer to the [http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson+as+a+Windows+service Hudson Wiki]. |
| | 15 | * This installs the Hudson slave as a Windows service that runs as the Local `SYSTEM` user. While normally not a problem, this can really cause problems if you need to do anything custom with your Subversion configuration (e.g. accepting self-signed or invalid SSL certificates). To fix this, continue with the following steps. |
| | 16 | * Create a local `hudson` user by going to Start -> Settings -> Control Panel -> Administrative Tools -> Computer Management -> Local Users and Groups |
| | 17 | * Edit the permissions for the Hudson slave workspace (e.g. `C:\Hudson`) and grant Full Control to the `hudson` user. Be sure to click the Advanced button and select the check box to "Replace permission entries on all child objects with entries that apply to child objects." |
| | 18 | * Edit the properties for the Hudson Slave service (in Start -> Settings -> Control Panel -> Administrative Tools -> Services). On the "Log On" tab, switch the "Log on as:" from the Local System account to the Hudson account. |
| | 19 | * '''Working with Subversion''' |
| | 20 | * Hudson uses SVNKit as it's embedded Subversion client. The Subversion configuration is stored in `%HOMEPATH%\Application Data\Subversion`. For most computers, this will be `C:\Documents and Settings\hudson\Application Data\Subversion`. |
| | 21 | * If you have a repository that needs authentication or has a broken SSL certificate (i.e. expired or self-signed), check out the repository on another machine where you can log in with a working subversion client. Then, copy the relevant files (i.e. from `~/.subversion/auth/svn.simple/` or `~/.subversion/auth/svn.ssl.server/`) into the corresponding location in the hudson user's configuration. |
