<< Back to previous view |
[QB-628] Subversion plugin has to specify "--no-auth-cache" option
|
|
Status: | Resolved |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | 3.0.4 |
Fix Version/s: | None |
Type: | Improvement | Priority: | Minor |
Reporter: | Alexey Shumkin | Assigned To: | Robin Shen |
Resolution: | Won't Fix | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown | ||
Environment: |
plugin Subversion Integration 3.0.6
OS Version: 5.1.2600 Service Pack 2 Build 2600 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free Original Install Date: 30.11.2008, 23:51:24 System Up Time: 3 Days, 17 Hours, 46 Minutes, 54 Seconds System type: X86-based PC Processor(s): 1 Processor(s) Installed. [01]: x86 Family 15 Model 6 Stepping 2 GenuineIntel ~2998 Mhz System Locale: ru;Russian Input Locale: en-us;English (United States) Time Zone: (GMT+03:00) Moscow, St. Petersburg, Volgograd Total Physical Memory: 2047 MB Available Physical Memory: 540 MB Virtual Memory: Max Size: 2048 MB Virtual Memory: Available: 2008 MB Virtual Memory: In Use: 40 MB |
Description |
Prerequisites:
QB is running under logged into OS user QB config uses Subversion repository. Subversion user specified in config is differrent then OSuser uses to access SVN repo (e.g. "svnbrowser" & "svncommitter" accordingly, and, for the worse,"svnbrowser" has read-only access) Steps After building a config, SVN "svnbrowser" auth requisites are cached, so "svn commit" fails and OSuser has to specify svn --username to replace auth cache That is annoying behaviour Subversion plugin has to use "--no-auth-cache" option to run checkout (as Luntbuild does) |
Comments |
Comment by Robin Shen [ 20/Sep/10 01:17 AM ] |
Adding "-no-auth-cache" will make it impossible to cache server certificate if connection is done through ssh or https, and may result in hanging builds. In normal cases, caching credentials will not be a problem as QuickBuild server and build agents should be running from a different machine other than developer's local machine. |
Comment by Alexey Shumkin [ 20/Sep/10 07:02 AM ] |
But accordingly to QB WIKI (http://wiki.pmease.com/display/qb30/Working+with+Subversion)
>>Handling https and svn+ssh schema >>To connect to Subversion repository with https and svn+ssh schema, you'll need to permanently accept the Subversion server's certificate from the command line before running QuickBuild. The detailed step is: >>Login to the build machine as the user that will be used to launch QuickBuild process. >>Connect to your Subversion repository using Subversion command line, and if the server asks for whether or not to save credentials for subsequent usage, choose "yes". >>Make sure that subsequent Subversion command does not prompt for username and password. >>Start QuickBuild process. So, why --no-auth-cache does matter here? |
Comment by Robin Shen [ 20/Sep/10 08:19 AM ] |
The wiki is no accurate. QB is able to accept permanent server certificate programmatically at start of a build, and this requires that option "--no-auth-cache" is not present, otherwise, Subversion will only accept certificate temporarily. |