|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 16/Nov/16 02:31 PM
Updated: 13/Jan/17 02:02 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
6.1.31
|
| Fix Version/s: |
6.1.36,
7.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
RHEL
|
|
|
Builds where working fine ( 11 successful builds) and then suddenly the variable used in the "User Name" of the Perforce repository was not being resolved resulting in the exception below
ccess for user '${vars.getValue("p4RepoUser")}' has not been enabled by 'p4 protect'.
14:07:16,287 ERROR - Error pumping stream.
com.pmease.quickbuild.QuickbuildException: Failed to run command: p4 -p perforce.lavastorm.com:1666 -u ${vars.getValue("p4RepoUser")} login -p
Command return code: 1
Command error output: Access for user '${vars.getValue("p4RepoUser")}' has not been enabled by 'p4 protect'.
|
|
Description
|
Builds where working fine ( 11 successful builds) and then suddenly the variable used in the "User Name" of the Perforce repository was not being resolved resulting in the exception below
ccess for user '${vars.getValue("p4RepoUser")}' has not been enabled by 'p4 protect'.
14:07:16,287 ERROR - Error pumping stream.
com.pmease.quickbuild.QuickbuildException: Failed to run command: p4 -p perforce.lavastorm.com:1666 -u ${vars.getValue("p4RepoUser")} login -p
Command return code: 1
Command error output: Access for user '${vars.getValue("p4RepoUser")}' has not been enabled by 'p4 protect'. |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Resolved
Major
Variable not being resolved in Perforce repository