Changes between Version 4 and Version 5 of Hudson/FAQ


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

--

Legend:

Unmodified
Added
Removed
Modified
  • Hudson/FAQ

    v4 v5  
    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." 
    1818  * 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`. 
     19 
     20=== How do I get Subversion working on a new Slave? === 
     21  * Hudson uses SVNKit as it's embedded Subversion client.  The Subversion configuration is stored in user's home directory. 
     22    * '''On Linux:''' `~/.subversion` 
     23    * '''On Windows:''' `%HOMEPATH%\Application Data\Subversion`.  For most computers, this will be `C:\Documents and Settings\hudson\Application Data\Subversion`. 
    2124      * 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`. 
    22     * 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. 
     26  * Also, don't forget to correctly configure Subversion for the SRN proxy.  The standard `servers` fragment we use on the SRN is: 
     27    {{{ 
     28[groups] 
     29son = software.sandia.gov 
     30srn = *.sandia.gov 
     31 
     32[srn] 
     33http-proxy-exceptions = *.sandia.gov 
     34 
     35[son] 
     36# (use default global proxy) 
     37 
     38[global] 
     39http-proxy-exceptions = localhost 
     40http-proxy-host = wwwproxy.sandia.gov 
     41http-proxy-port = 80 
     42    }}}