 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Robin Shen [01/Feb/18 11:56 PM]
Can you please attach the whole build log with step name information included?
Hi,
Here the checkout step detail, its a perforce use. Name checkout Type Checkout Description not defined Enabled yes Execute Condition If all previous sibling steps are successful Node Selection On specified build agent Build Agent AGENT:8811 Inheritable yes Repository P4-REPOSITORY Node Preference Prefer least loaded node Pre-Execute Action No action Post-Execute Action Execute a script Script groovy:vars.get("PerforceSyncCL").setValue(repositories.get("P4-REPOSITORY").getRevision().toString()) Repeat Parameters not defined Fetch Input Files not defined Send Output Files not defined Timeout 0 Retry Upon Failure not defined ----------------------------------------------- And here the full log : INFO - Executing pre-execute action... INFO - Running step... INFO - Checking step execute condition... INFO - Step execute condition satisfied, executing... INFO - Executing pre-execute action... INFO - Running step... INFO - Checking out revision 666 of repository 'P4-REPOSITORY'... WARN - Client 'client_AGENT' can only be used from host 'client_SERVER'. INFO - Executing post-execute action... ERROR - Step 'master>checkout' is failed: Failed to run command: "C:\Program Files\Perforce\p4.exe" -p server:66 -u user -P ****** -c client_AGENT revert -w //... Command return code: 1 Command error output: Client 'client_AGENT' can only be used from host 'client_SERVER'. Sorry I am not clear previously. When show the build log, there is a checkbox "show step info". Please check that option and download the build log. Please also include the repository definition.
Hi, thanks for the details so here the log with step :
[master>checkout@AGENT:8811] INFO - Checking step execute condition... [master>checkout@AGENT:8811] INFO - Step execute condition satisfied, executing... [master>checkout@AGENT:8811] INFO - Executing pre-execute action... [master>checkout@AGENT:8811] INFO - Running step... [master>checkout@AGENT:8811] INFO - Checking out revision '666' of repository 'P4-AGENT_REPOSITORY'... [master>checkout@AGENT:8811] WARN - Client 'USER_AGENT' can only be used from host 'SERVER'. [master>checkout@AGENT:8811] INFO - Executing post-execute action... [master>checkout@AGENT:8811] ERROR - Step 'master>checkout' is failed: Failed to run command: "C:\Program Files\Perforce\p4.exe" -p perforce:77 -u USER -P ****** -c USER_AGENT revert -w //... Command return code: 1 Command error output: Client 'USER_AGENT' can only be used from host 'SERVER'. It seems that client USER_AGENT want to be used on SERVER host. Please see the repository definition on attach file. Please do not use the option "Use specified client name" as this option will always use the same client name even if multiple clients are used across different machines. Please use the auto-generated name based on configuration and path.
Hi,
I can't use this kind of workspace, my workstation use client hardcode name, use on other software and i don't want to change it. I have already try this solution but the generated workspace name don't respect my name convention... That i don't understand its why the SERVER try to use the client workspace from AGENT, why it do this.... Thanks for your respond. Using specified name is fine, but you need to configure your master step running on AGENT also. That is to say:the master step, the checkout step and the label step (if you have) should all running on the same machine (AGENT here).
Thanks Robin for all your help.
I was using on Node selection the option : "On node with specified resource" using Ressource from AGENT, but i will try the 'On specified build Agent' on AGENT to test. Tell you if its better ! Another thanks, your help is really appreciated. OK its not work the way intended, configuration are started without wait for the node just start multi configuration on the same node... so i re-put the "on node with specified ressource' because i don't want my agent start configurations without wait for previous check to be done.
If you hard-code the perforce client name, you should make sure that all steps of the build runs on same machine. You may specify your node selection setting as:
if all criterias are matched: the first criteria: your previous resource match criteria the second criteria: on the AGENT node This way the build will only run on AGENT node but will also wait for the resource to be available. I noticed that you are using the same value for "Client Name" and "Existing Client Name". "Existing Client Name" should be specified as an existing client used as template for QB client. It should be pre-created manually and the name should be different from "Client Name" used by QB for build purpose. Please use a different name, and make sure that:
1. Existing client name is created before-hand. 2. Client name should not be exist before-hand (will be created by QB). If it already exists, please delete it first. This works at my side with your setting, so not sure what happens? Are you able to reproduce this issue with a sample database and then send the backup to me for demonstration?
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Blocker
Perforce Plugin - can only be used from host (switch host for P4 workspace)
