If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/Aug/11 04:07 PM
Updated: 03/Aug/11 03:05 PM
|
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
QuickBuild 4.0.0-M1, 2011-07-02, Windows 7 agent with RedHat 5 server.
|
|
I have set up a QB user agent on my desktop. Having checked out the code, made some changes, and, run them through a proof build, I then check in and find that the user under which they were checked in was the QuickBuild user, as defined in the repository under Proof Build Support.
It appears that QuickBuild is caching the authentication tokens when it performs local SVN operations via the user agent. This would not be a problem if I were running the user agent as the local system account. However, I am running it via 'agent console', so the user agent is running as me, so the cached authentication tokens are overwriting my own.
To prevent this from happening, Subversion commands executed by the user agent should be run with the '--no-auth-cache' option.
|
Description
|
I have set up a QB user agent on my desktop. Having checked out the code, made some changes, and, run them through a proof build, I then check in and find that the user under which they were checked in was the QuickBuild user, as defined in the repository under Proof Build Support.
It appears that QuickBuild is caching the authentication tokens when it performs local SVN operations via the user agent. This would not be a problem if I were running the user agent as the local system account. However, I am running it via 'agent console', so the user agent is running as me, so the cached authentication tokens are overwriting my own.
To prevent this from happening, Subversion commands executed by the user agent should be run with the '--no-auth-cache' option. |
Show » |
|
In the event we do add the ability for QB to check in the users' changes (unlikely considering our workflow), I would of course be querying the user for her password. However, even set up that way, I would not want to cache the authentication tokens, as the user may for her own reasons, or for company security policy, not be caching them on her system. As you do not want to disturb the user's working copy, you should not disturb the user's working environment, either.
However, I can understand if you want to treat this as an enhancement request rather than a bug.