Team Environment ?
Moderator: SourceGear
-
- Posts: 2
- Joined: Wed Aug 10, 2005 12:07 pm
Team Environment ?
We have recently purchased Vault and we are moving (adding) our web applications to Vault. We are trying to use Vault with programmer teams where the working directory(s) is on a staging server. We have a few large web applications that have multiple projects under them. The programmers keep a full working version of the web applications on their desktop for unit testing purposes. ... Checkouts are made to the staging server, then the programmer will copy the source to his desktop for modications, unit testing, etc. He will then copy the program back to the staging server, test, and then checkin back to Vault. This seems to be working except when another programmer goes to the Vault Repository / Folder, it shows the program as a Renegade. Is there anyway to get around this. Thanks!
-
- Posts: 2
- Joined: Wed Aug 10, 2005 12:07 pm
All of the programmers are using the same working directory when checking out, making a change, checking in a program change for the same Project. They are not working on the same Project at the same time, but Programmer A may make a change today and Programmer B may make a change next week. One of our .NET Web Apps is one Solution with many Projects under it. The programmers make the program changes on their local desktop, test on local, move the changed program up to the staging server, test, and then check in the program source back in Vault. ... Is there a better way to work in a "team" environment on the same web app solution? Could you provide an example of how we should set up the staging / test server and programs checkout to it and then work on their "local" desktops?
Thanks for your help!!!
Thanks for your help!!!
You could continue to work as you are and be prepared to see files that have a "renegade" status. This status can be resolved by performing a "get latest". However, this typically is not how Vault is used. Please review the following KB article that explains how the Vault client works and gives details on working folder data.
http://support.sourcegear.com/viewtopic.php?t=562
Another Vault function that may helpful would be Shadow Folders. A Shadow Folder is a local folder that contains the contents of a repository folder, and is kept up-to-date in the shadow folder by the Vault Server as changes are applied to the repository folder. Shadow Folders can be enabled using the Vault Admin Tool.
Please let me know if you have any more problems or questions.
Thanks,
Tonya Nunn
http://support.sourcegear.com/viewtopic.php?t=562
Another Vault function that may helpful would be Shadow Folders. A Shadow Folder is a local folder that contains the contents of a repository folder, and is kept up-to-date in the shadow folder by the Vault Server as changes are applied to the repository folder. Shadow Folders can be enabled using the Vault Admin Tool.
Please let me know if you have any more problems or questions.
Thanks,
Tonya Nunn