| Key: |
QB-2590
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Won't Fix
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
J. Mash
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 02/Dec/15 02:22 AM
Updated: 15/Dec/15 02:13 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Mac 10.10, Windows Server 2012, Centos 6.6
|
|
|
When using the 'Record Changes' feature on a Perforce repository, it does not appear to create the workspace being referenced (using the settings specified in the repository definition) when it does not exist, nor does it emit any sort of error or warning indicating that it doesn't exist.
In this regard, it would be ideal if it worked in much the same way as the 'Checkout' feature.
|
|
Description
|
When using the 'Record Changes' feature on a Perforce repository, it does not appear to create the workspace being referenced (using the settings specified in the repository definition) when it does not exist, nor does it emit any sort of error or warning indicating that it doesn't exist.
In this regard, it would be ideal if it worked in much the same way as the 'Checkout' feature. |
Show » |
| No work has yet been logged on this issue.
|
|
Record Changes with Perforce Workspace Issue