Using the same workspace from two different machines
Is it possible to share the same workspace in two different machines? I want to develop on my work machine and then check in the files and access them through my lab machines.
I use the command line interface in both the machines. Is it possible to use Jazz this way? |
4 answers
You can use jazz SCM that way ... you will just need to be careful about
what files you edit on either machine. If you are not modifying the same items, then it is pretty straightforward. When you try and modify a workspace which is "out of sync", a dialog will come up to walk you through the process. HTH, JohnC Jazz SCM anandsan wrote: Is it possible to share the same workspace in two different machines? |
Thanks John.
I used the command line tool and this is what happened. I edited a file in my linux workstation and checked it in. In the windows workspace which was not changed, I did a scm load. I expected jazz to update my windows workspace with that one file I changed. Instead scm load complained that there were local changes and I had to use the --force option to over ride my local files. Is there any way to do a smart partial update through the scm command line? |
Individual workspaces aren't meant to be modified from multiple clients. If you keep the two workspaces in lockstep (ie, only modify stuff on your linux box, then load onto the windows box, or vice versa) you won't risk losing changes.
To merge changes from multiple clients, you should create a workspace for each client and flow the changes back and forth. This goes for the GUI as well as the CLI. e |
Thanks again.
Assuming I stick to the one workspace and I edit in only one machine and use the other one just for builds: Using the CLI, is there a way to do partial updates? The only option I see today is to do scm load --force which refreshes the entire tree. Or should I not depend on Jazz for this and setup rsync or something similar? |
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.