We have a configuration (conf_A) that inherits its repositories from the parent configuration (conf_B), but does not actually use or need them in the workflow.
At the beginning of each build in conf_A, Perforce tries to get updates from all these inherited repositories.
In log this looks like:
Getting changes of 'some_repository' since build 'buildID'...
Perforce user on the agent, where conf_A runs, does not have access to all the repositories inherited from conf_B.
So the build aborts with this message:
Failed to run command: p4 -p <perf_server>:<port> -u <user> -P <passwd> -c <agent>-8379 client -i
Command return code: 1
Command error output: Error in client specification.
Question: is this behavior "works as designed" - that all the repositories of the configuration (incl. the inherited ones) are updated at the beginning of each build, no matter whether they are used in the worklfow or not?
- solved #2
- replies 7
- views 510
- stars 1