|
|
|
[
Permlink
| « Hide
]
Robin Shen [26/Jul/14 01:09 AM]
QB already has this ability: when define "client specification" of a perforce repository, you may select the option "Create client based on specified stream" to use stream oriented client.
This is not what I mean Robin. I want to specify a stream view and do advanced view specification on this. I can do a client specification of course, but then if you check workspace view with p4 client -o then stream field is empty.
I just checked and QB does able to create stream-based client if that option is used. This is what I am doing:
1. create a perforce repository using option "Create client based on specified stream" and then specify a stream. 2. run the build, and a client has been created automatically for the build, run "p4 client -o <build client>" and the output does indicate that the client is based on specified stream. Can you please verify it again at your side? That is indeed working fine but I want to do:
1) create a perforce client based on a view specification like for example: //depot/example/... //xxx/... -//depot/example/notneeded/... //xxx/... Where example is a perforce stream 2) p4 client -o has then empty stream field but filter view, while I want both stream and view having a value It seems that as long as a view is attached to a stream, Perforce does not allow you to configure the mapping freely as non-stream client. Instead it gives below message:
To edit the mappings, you must edit the stream's path So the only thing we can do for a stream based client here is to specify the stream name. that would be preferred and the intention of this feature request.
OK I see. You want to be able to configure stream path directly via QB interface. I am not sure if this is doable via QB interface, and will investigate it. Reopened the issue for back log purpose.
I was trying to configure the a stream path via the QB interface and actually it is still not possible. Any plans to still add this support?
My last investigation does not result in any workable approach doing this by calling Perforce command line, so still do not have a timeline for it yet.
|