What is the use case for lscm changeset extract?
I am trying to extract files to a local path from a changeset. I'm trying this:
c:\ws1>lscm.bat changeset extract -r local -w "ws2" -d "dir" 1111 "/p1/file.bat" "dir/p1/file.bat"
However, I get this error:
Problem running 'changeset extract':
I thought I'd used this command in past with success, but perhaps I was in a sandbox already for ws1. For the life of me I can't figure out why you would use this command if you were already in a sandbox. But if I try to specify a directory outside of my current sandbox, I get this:
c:\ws1>lscm.bat changeset extract -r local -w "ws2" -d "c:\temp" 1111 "/p1/file.bat" "/p1/file.bat"
What I want to do is extract files from a changeset on the server to a non-shared filepath on my local. Is that possible? If not, what is the purpose of lscm changeset extract?
Thanks!
Andy
Update 3/20/14 -- the initial question is answered (see below) but interestingly, it seemed like it could not locate the changeset while I was in a sandbox:
Note:
c:\ws1>lscm -u y ls changes -r local -w "ws2" 1187 |
Accepted answer
The -d option is used to specify the root of the shared file system i.e if you are running the command from outside the sandbox root, it should be used.
You may try
Andy Jewell selected this answer as the correct answer
Comments
Andy Jewell
commented Mar 20 '14, 10:51 a.m.
Thank you, Karthik! That worked. I found something interesting, though. When I was in a sandbox it would not recognize the change within the changeset. Please see the additional edit in the original question. This this expected behavior?
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.