[#QB-2590] Record Changes with Perforce Workspace Issue

QuickBuild

Record Changes with Perforce Workspace Issue

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

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [15/Dec/15 02:13 PM]

Just tested this and it seems that QB handles it correctly: the workspace folder will not be created on disk as this is how this step intends to do. However the client itself will be created on Perforce server if it does not exist already.

Change by Robin Shen [15/Dec/15 02:13 PM]
Field	Original Value	New Value
Status	Open [ 1 ]	Closed [ 6 ]
Resolution		Won't Fix [ 2 ]