First Question:
I was wondering if you have 3 versions of a file you get back to version 1. Do you just get the version 1 file and copy it over the version 3 file and check it in to create version 4? or do you do something else?
Second Question:
Can you create a baseline? So you can say I want version 4 of 5 of this module and version 2 of 6 of this module to create a build and all you have to do it check out the baseline. Just wondering if you can do that.
Thanks
Vega
Vault newbie questions
Moderator: SourceGear
-
Mike Dimmick
- Posts: 28
- Joined: Tue Feb 17, 2004 7:42 am
- Location: UK
- Contact:
1. Right-click the file, choose Show History. Click OK to accept the default query.
If you want to temporarily use version 1, right-click version 1 and choose Pin. To permanently roll back to version 1 and make it version 5, choose Rollback.
2. You can create a label that will do what you want - right-click the project and choose Label. When you want to get a particular label, right-click the project and choose Show Labels. Right-click the label in the Show Labels window and choose Get.
It's possible but hard to add labels retrospectively. I think you have to Pin the file versions you want to include in the label, then perform the Label operation. You can then unpin everything. Alternatively, you can go to a particular version of the project. Right-click the project and choose Show History. Select 'View Folder History by Version', then click OK. You can now label a particular version of the project.
If you want to temporarily use version 1, right-click version 1 and choose Pin. To permanently roll back to version 1 and make it version 5, choose Rollback.
2. You can create a label that will do what you want - right-click the project and choose Label. When you want to get a particular label, right-click the project and choose Show Labels. Right-click the label in the Show Labels window and choose Get.
It's possible but hard to add labels retrospectively. I think you have to Pin the file versions you want to include in the label, then perform the Label operation. You can then unpin everything. Alternatively, you can go to a particular version of the project. Right-click the project and choose Show History. Select 'View Folder History by Version', then click OK. You can now label a particular version of the project.
Mike suggests some good pointers.
There are three other ideas that I'd like to add which address your baseline question.
1) If the file versions existed together at some point in time ( version 5 of module A and version 2 of module B both exist on a particular date ), you could view the history of the parent folder - make sure to use the "View folder history by version" option. Find the version of the folder for that given date. ( Use View Tree to make sure the folder is the correct version. ) Now you can either label, pin, or branch that version of the folder to recreate your baseline
2) If the file versions have never existed at that point in time in the folder, but the files do exist, you could create a label on the version of the folder which best matches your overall picture of the baseline using the "View folder history by version" option within history. Next, Label the desired version of the folder. Finally, you can use Label promotion to "fine-tune" the label - changing versions of files, adding files which exist in the current folder but not in the label, deleting files from the label.
3) It is very tedious, but you could also create a "customized" branch of the files you desire, but looking at the history of each item, and then branching each of the desired versions into a new location.
HTH
There are three other ideas that I'd like to add which address your baseline question.
1) If the file versions existed together at some point in time ( version 5 of module A and version 2 of module B both exist on a particular date ), you could view the history of the parent folder - make sure to use the "View folder history by version" option. Find the version of the folder for that given date. ( Use View Tree to make sure the folder is the correct version. ) Now you can either label, pin, or branch that version of the folder to recreate your baseline
2) If the file versions have never existed at that point in time in the folder, but the files do exist, you could create a label on the version of the folder which best matches your overall picture of the baseline using the "View folder history by version" option within history. Next, Label the desired version of the folder. Finally, you can use Label promotion to "fine-tune" the label - changing versions of files, adding files which exist in the current folder but not in the label, deleting files from the label.
3) It is very tedious, but you could also create a "customized" branch of the files you desire, but looking at the history of each item, and then branching each of the desired versions into a new location.
HTH
Jeff Clausius
SourceGear
SourceGear
More Newbie Questions
How should I integrate my current file structure with some of the proposed file structures?
My Current Folder Structure
D:\[SolutionName]\
D:\[SolutionName]\[ProjectName]\
What I believe to be an example of a folder structure that is using SCM
$/[ProductName]/
$/[ProductName]/trunk/
$/[ProductName]/trunk/src
$/[ProductName]/trunk/docs
$/[ProductName]/trunk/tests
$/[ProductName]/branches/[branchname]/
$/[ProductName]/branches/[branchname]/src
$/[ProductName]/branches/[branchname]/docs
$/[ProductName]/branches/[branchname]/tests
$/[ProductName]/snapshots/[snapshotName]
I believe that D:\[SolutionName]\[ProjectName]\ MAPS TO $/[ProductName]/
I also believe that a Repository could map to a solution???
I am strating to feel like I am going to have to start using NAnt to build this. I hope the new version of NAnt is easier to use.
I am alone in the development department so I want something easy. But I am also Anal Retentive and want something clean and usable. The thought that I am going to have a million folders for branches and stuff puts me off, but I think as I understand it I will be more comfy with it.
What are some ways to handle Version 1.0 and the like. I am thinking of using labels on the TRUNK to mark version diff. And branching to fix bugs and then remerge when the bug is fixed.
I am taking this slow and I have read a lot on this forum which has some excellent discussions. I would love to see a newbie article here that has Best Practices, Examples, and Walk Throughs. Thanks guys for an excellent product!
My Current Folder Structure
D:\[SolutionName]\
D:\[SolutionName]\[ProjectName]\
What I believe to be an example of a folder structure that is using SCM
$/[ProductName]/
$/[ProductName]/trunk/
$/[ProductName]/trunk/src
$/[ProductName]/trunk/docs
$/[ProductName]/trunk/tests
$/[ProductName]/branches/[branchname]/
$/[ProductName]/branches/[branchname]/src
$/[ProductName]/branches/[branchname]/docs
$/[ProductName]/branches/[branchname]/tests
$/[ProductName]/snapshots/[snapshotName]
I believe that D:\[SolutionName]\[ProjectName]\ MAPS TO $/[ProductName]/
I also believe that a Repository could map to a solution???
I am strating to feel like I am going to have to start using NAnt to build this. I hope the new version of NAnt is easier to use.
I am alone in the development department so I want something easy. But I am also Anal Retentive and want something clean and usable. The thought that I am going to have a million folders for branches and stuff puts me off, but I think as I understand it I will be more comfy with it.
What are some ways to handle Version 1.0 and the like. I am thinking of using labels on the TRUNK to mark version diff. And branching to fix bugs and then remerge when the bug is fixed.
I am taking this slow and I have read a lot on this forum which has some excellent discussions. I would love to see a newbie article here that has Best Practices, Examples, and Walk Throughs. Thanks guys for an excellent product!