Hello Xailers,
We are testing the Xailer Version Control, but a doubt arrised, how do we work with multiple users, each user in a different branch?
The project is already on a mapped network drive, but each time we change the branch, it changes for every user.
We use the "Restore this revision" option to change branches because we saw no other option.
How do we manage the branches? Delete, edit, change,...
The Xailer IDE help is not very clear on how to setup it...
Thanks in advance,
Juliano
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
XVC Doubts
Re: XVC Doubts
Juliano,
None of the many existing VCS can be used in a shared folder. I mean that if you want to use a VCS (XVC, Git, SVN, HG, Fossil, Bzr, etc.) each user must have his own "working directory". It cannot reside in a shared folder in a server.
The way to use a VCS is to put the repository in a shared location (or a specific server if the VCS support it). Then, each user make a "checkout" (or whatever it's called in that VCS) into a local and private directory. That directory is called "working directory" in most VCS and it's usually located in the user local HDD, not in a server.
The users work in their own "working directories" all the time, and do "commits", "updates", "branches", "merges", etc., to the common repository. If you're using a DVCS (distributed version control system) like Git, HG, Fossil or Bzr, then there are two repositories: the one that is shared between users and another local and private. In a DVCS there are also commands to send and fetch data from/to your local repository to/from the shared one, like Push or Pull.
None of the many existing VCS can be used in a shared folder. I mean that if you want to use a VCS (XVC, Git, SVN, HG, Fossil, Bzr, etc.) each user must have his own "working directory". It cannot reside in a shared folder in a server.
The way to use a VCS is to put the repository in a shared location (or a specific server if the VCS support it). Then, each user make a "checkout" (or whatever it's called in that VCS) into a local and private directory. That directory is called "working directory" in most VCS and it's usually located in the user local HDD, not in a server.
The users work in their own "working directories" all the time, and do "commits", "updates", "branches", "merges", etc., to the common repository. If you're using a DVCS (distributed version control system) like Git, HG, Fossil or Bzr, then there are two repositories: the one that is shared between users and another local and private. In a DVCS there are also commands to send and fetch data from/to your local repository to/from the shared one, like Push or Pull.
Re: XVC Doubts
Hello José!
Many thanks for the help!! We made the changes and now it is working flawlessly
There is just one doubt left, if for any reason we need to change the directory of the .XVC files, how should we proceed?
I am asking this because we tested this routine, and when we changed the revision (before the dir change), the directory of the XVC on the properties changed as well to the old directory, breaking the revision history.
Thanks!
Many thanks for the help!! We made the changes and now it is working flawlessly
There is just one doubt left, if for any reason we need to change the directory of the .XVC files, how should we proceed?
I am asking this because we tested this routine, and when we changed the revision (before the dir change), the directory of the XVC on the properties changed as well to the old directory, breaking the revision history.
Thanks!
Re: XVC Doubts
Juliano,
there are 2 ways to do:
1) Just move your .xvc file into the new directory, and modify the path in the "project properties".
2a) Run XVC -> Update
2b) Move the .xvcw file into your project's root folder.
3) Finally do a "commit"
You must do 1), 2a) and 3) or 1), 2b) and 3)
there are 2 ways to do:
1) Just move your .xvc file into the new directory, and modify the path in the "project properties".
2a) Run XVC -> Update
2b) Move the .xvcw file into your project's root folder.
3) Finally do a "commit"
You must do 1), 2a) and 3) or 1), 2b) and 3)
Re: XVC Doubts
Hello José,
I tried doing what you said but it did not work completely...
Here is what I did:
1) Created a project, enabled XVC, Updated, Commited (Revision 1, XVC Directory C:\DIR1\);
2) Altered the directory, updated, commited (Revision 2, XVC Directory C:\DIR2);
3) Restored the Revision 1, the XVC Directory changed back to C:\DIR1;
I understand that it happens because the files are restored,
but when we update this property in the project, shouldn't it update for all revisions?
Thanks again,
Juliano
I tried doing what you said but it did not work completely...
Here is what I did:
1) Created a project, enabled XVC, Updated, Commited (Revision 1, XVC Directory C:\DIR1\);
2) Altered the directory, updated, commited (Revision 2, XVC Directory C:\DIR2);
3) Restored the Revision 1, the XVC Directory changed back to C:\DIR1;
I understand that it happens because the files are restored,
but when we update this property in the project, shouldn't it update for all revisions?
Thanks again,
Juliano