Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
hi,
I dont know if this is a Quickbuild problem or Subversion.
I have a machine with build agent, which many users do checkouts and commits, with different permissions, but this is done in the middle of the build.
But if I put the username and password in the repository, Subversion caches the password. if I put store-passwords = no and store-auth-creds = no, I cant commit after.
example:
Build agent A
=================
Checkout and commit
[repository W] user X
[repositoy Y] user Z
I dont know how to do this. <!-- s:cry: --><img src="{SMILIES_PATH}/icon_cry.gif" alt=":cry:" title="Crying or Very sad" /><!-- s:cry: -->
-
replies
5
-
views
1313
-
stars
0
-
How about specifying user name and password at commit time also?
[quote="robinshine"]How about specifying user name and password at commit time also?[/quote]
but the password cant stay in the build because the build can be run on the developer's machine and cant commit with that password.
if I pass the password by Quickbuild, the developer can display the password by build.
I am a bit confused. Build agent normally runs on a standalone machine instead of developer's machine. Can you please explain your usage scenario in more detail? Thanks.
Build_Agent_A
===========================================================================================================================================================================
(run a lot of builds, containing checkouts and commits in svn repositories: svn_user_A, svn_user_B, with different permissions)
------
Quickbuild Build_ABC
===================
Step Build_A (using visual build or python), running in this Build_Agent_A, with permissions svn_user_A with commits.
Quickbuild Build_XYZ
===================
Step Build_B (using visual build or python), running in this Build_Agent_A, with permissions svn_user_B with commits.
------
by quickbuild, i do the checkout svn repo and run these Builds.
in Build_Agent_A can commit files, but not on developer's machine.
------
scenario 1
if i set the user and password in the svn repo on quickbuild, the Build_Agent_A subversion, cache authentication in the first build that run. So i cant checkout other build with other permission.
scenario 2
if i set in the subversion (on Build_Agent_A) to "no cache the authentication and password", so i have to put the user and password in Build_A and Build_B, but if i set a secret variable (SVN_USER and SVN_PWD) on quickbuild and pass to Build_A and B, inside the build (visual build or python), the developer can show this password variable.
I hope the explanation has been clearly. <!-- s:cry: --><img src="{SMILIES_PATH}/icon_cry.gif" alt=":cry:" title="Crying or Very sad" /><!-- s:cry: -->
Thanks I understand your approach now. But unfortunately there is no easy way to work around this as by the nature you have to explicitly specify the account to commit code and you can not prevent user from checking the password since they have full control of the script. Actually the user can do anything to the system by injecting desired logic.
