Two builds agent and svn permissions #2211

kdelrey · 1 decade ago

i have 1 build with steps in 2 different build agents with svn permissions differents.

BUILD X
===================================================

configured svn repository Y, user yyy password yyy

Step Sequential 1 - Build Agent A - svn permission
- checkout
- run build

Step Sequential 2 - Build Agent B - without svn permission
- run build

How to configure repository (with user and password) in this build and dont return error?

Failed to run command: svn info http://xxxx --username xxx --password *** --xml 
Command return code: 255

replies 16
views 4511
stars 0

robinshen ADMIN · 1 decade ago

Do you have any script or step running on Agent B using that subversion repository? By default QB should not run subversion commands for a builder step.

kdelrey · 1 decade ago

[quote="robinshine"]Do you have any script or step running on Agent B using that subversion repository? By default QB should not run subversion commands for a builder step.[/quote]

nothing... the step doesnt have checkouts or use svn repository.

robinshen ADMIN · 1 decade ago

Can you please send backup of your database to [robin AT pmease DOT com] and also let me know the build and step to check?

kdelrey · 1 decade ago

i had selected the main node "on build requester's user agent" that had cached the svn password with another permission... and created a sequential composition with checkout (svn repository configured with a user and password with oher permission) and run build in other agent.
it's not worked. <img src="{SMILIES_PATH}/icon_cry.gif" alt=":cry:" title="Crying or Very sad" />

now, i created a sequential composition with "on build requester's user agent", and inside this composition i created other composition running in another agent.
now, its works. <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing" />

i didnt understand. but now is ok. <img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes" />

robinshen ADMIN · 1 decade ago

Hmm. Seems odd. Just send me the database backup and let me know reproducing steps if you encounter the issue again.

kdelrey · 1 decade ago

happened again <img src="{SMILIES_PATH}/icon_cry.gif" alt=":cry:" title="Crying or Very sad" />

its simple to reproduce...

eg:

this build pause the qb, do the sync the storage (on agent with svn) and resume.

BUILD 1 - running ON SERVER (dont have svn installed)
========================================

STEP 1 - pause

STEP 2 - SEQUENTIAL - sync the storage ON AGENT A (with svn installed)
STEP 2.1 - checkout subversion repository
STEP 2.2 - run the synchronize the storage

STEP 3 - resume

error:

Cannot run program "svn" (in directory "C:\quickbuild-5.0.11\bin"): CreateProcess error=2, O sistema não pode encontrar o arquivo especificado

i believe its not necessary to send the database backup.
its too easy to reproduce, only have 1 build containing two agents, one with svn and other without svn. and a repository configured.

tks.

robinshen ADMIN · 1 decade ago

Master step has to be run on a machine with subversion installed as QB takes subversion repository snapshots on that machine to get the head revision.

kdelrey · 1 decade ago

[quote="robinshine"]Master step has to be run on a machine with subversion installed as QB takes subversion repository snapshots on that machine to get the head revision.[/quote]

ok... but...
and when has 2 agentes and 2 repositories with different permissions?

#10

robinshen ADMIN · 1 decade ago

QB always carrys defined user name and password information to interact with Subversion. Even if user/password is different on different agents, you can script it for instance:

${node.getAttribute("repo1_user")}
${node.getAttribute("repo1_password")}

Here "repo1_user" and "repo1_password" are user attribute defined in agent in case they are different on different agents.

#11

kdelrey · 1 decade ago

i tried this, but the build stay "CHECKING_BUILD_CONDITION"...

because the agent saves the user and password (svn cache authentication)
its not necessary to configure the user/pwd.

i guess the quickbuild dont respect the checkout repository on specified agent.

#12

robinshen ADMIN · 1 decade ago

QB always connects to Subversion using explicit user/pass. Can you please create a simple database demonstrating your problem, and send to [robin AT pmease DOT com]?

#13

kdelrey · 1 decade ago

[quote="robinshine"]QB always connects to Subversion using explicit user/pass. Can you please create a simple database demonstrating your problem, and send to [robin AT pmease DOT com]?[/quote]

hummm... i put the user/pass in repository and works fine... so is too better configure the password on qb instead of save the svn password on agent.
i'll use this way ... anything I post my doubt again.
thanks

#14

kdelrey · 1 decade ago

[quote="robinshine"]QB always connects to Subversion using explicit user/pass. Can you please create a simple database demonstrating your problem, and send to [robin AT pmease DOT com]?[/quote]

if has the user/pass on repository, anybody can do the checkout this repository. and there repositories that only can do the checkout in particular machine/agent.
the ideal is to save the password in the machine, but isnt work, because gives denied access.

scenario: (its simple, dont have need to send you a database)

i have a build that run on AGENT A...
STEPS:
1-checkout repository A using SUBVERSION_USER A
2-run the build
3-sequential step( runs on AGENT B)
3.1-checkout repository B using SUBVERSION_USER B
3.2-run the build

#15

robinshen ADMIN · 1 decade ago

QB has to interact with every Subversion repositories on master node to determine current head revisions, and not specifying repo user/pass explicitly will confuses QB.

#16

kdelrey · 1 decade ago

this is a bug

#17

robinshen ADMIN · 1 decade ago

I would think this is rather a limitation than a bug.