Changes between Version 5 and Version 6 of Hudson/FAQ


Ignore:
Timestamp:
03/24/09 16:57:59 (10 years ago)
Author:
jdsiiro
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Hudson/FAQ

    v5 v6  
    1313=== How do I configure a Windows Slave? === 
    1414  * 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. 
     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).  Additionally, running Hudson as a privileged user presents a security risk.  To fix this, continue with the following steps to run Hudson as a non-privileged local user. 
    1616  * Create a local `hudson` user by going to Start -> Settings -> Control Panel -> Administrative Tools -> Computer Management -> Local Users and Groups 
    1717  * 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." 
     
    2323    * '''On Windows:''' `%HOMEPATH%\Application Data\Subversion`.  For most computers, this will be `C:\Documents and Settings\hudson\Application Data\Subversion`. 
    2424      * If you run the Hudson Slave service as the Local `SYSTEM` user, the Subversion configuration will probably be stored in `C:\WINDOWS\system32\config\systemprofile\Application Data\Subversion`. 
    25   * 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. 
     25  * 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. 
    2626  * Also, don't forget to correctly configure Subversion for the SRN proxy.  The standard `servers` fragment we use on the SRN is: 
    2727    {{{