I am glad to say that we are using vault. Here I got few fundamental questions about vault usage. Please let me know the answers for these below questions.
1. How to get files based on Label. For Ex: My solution has 10 projects. I have labeled version 1.0 and deployed the application. Now I got a CR from my users. As per the request I have modified only project 5 & Project 6. Now I have deployed the application again with these changes. In the next iteration I have modified project 2. (What version you suggest for this change 1.1 or 1.2?). Assume I have labeled as 1.2, now I want to get 1.1 files based on my label. How can I get the labeled files at root level…So I can get all the files at a time?
2. In an enterprise application how many repositories you suggest (Development, Integration, Staging and Production stages. One/Two/One for each stage?). As you know repository export option is not available now. What is the vault team approach to maintain repositories? Are you suggesting only one repository for the entire project life cycle? Or multiple repositories for different stages? Or any better solution you have? Please let me know your suggested approach.
3. I have deployed my app with label 1.0 at source code version no 5.0 and my current development source version is 9.0. I want to modify production version for bug fix. Based on single repository approach, how can I modify one file and compile source code version 5.0. If multiple repositories, how will we make sure that developers checked out correct version of the file from correct repository with out any problem.
Please let me know, and thanks for all your help!
Suggestions please…
Moderator: SourceGear
-
sreeni2219
- Posts: 1
- Joined: Fri May 06, 2005 7:29 am
- Contact:
1. How to get a label. Assuming that you have the following structure:
$/product/project1
$/product/project2
$/product/project3
...
All labels should be applied to $/product. You can then fetch all files for the product by right clicking $/product and choosing show labels. You can then download any of the labels in the show labels dialog.
2. If you're moving code from one stage to another, I would recommend using one repository and utilizing Merge Branches to get code from one branch to another.
For more on branches, look at http://software.ericsink.com/scm/scm_branches.html
3. You've described a case where you need to create a new branch from your 1.0 label. We'll call that branch 1.0.1. You can then make the bug fix to the 1.0.1 branch and use merge branches when you want to get that bug fix back into the trunk. You can branch a label with the show labels dialog.
$/product/project1
$/product/project2
$/product/project3
...
All labels should be applied to $/product. You can then fetch all files for the product by right clicking $/product and choosing show labels. You can then download any of the labels in the show labels dialog.
2. If you're moving code from one stage to another, I would recommend using one repository and utilizing Merge Branches to get code from one branch to another.
For more on branches, look at http://software.ericsink.com/scm/scm_branches.html
3. You've described a case where you need to create a new branch from your 1.0 label. We'll call that branch 1.0.1. You can then make the bug fix to the 1.0.1 branch and use merge branches when you want to get that bug fix back into the trunk. You can branch a label with the show labels dialog.