I have a StarTeam project. It has several directories. When I commit changes I don't want to have to search all the directories myself to find changed files.
How can I see all changed files in all directories in one list without searching myself?
I am using StarTeam 2009.
P.S. I come from Mercurial and TortoiseHg so it seems incredible to me that I can't seem to be able to do this easily in StarTeam.
On the Left side slect the root node of the tree then select the filter "All File By Status" and the short button "All descendant" beside!
With the context Menu from the Status Field you can group your Results.
Georg
Related
I need to checkout files from StarTeam 12.0 into my local folders.
The folder tree on starteam is like :
folder_top
folder_level_1a
subfolder_level_2
subfolder_level_3
folder_level_1b
folder_level_2
folder_level_3
But, after checking out all files in my specified local folder, all files (of folder_top) are located in one folder. All subfolders and their files are not checked out.
Any help would be appreciated.
Selecting your top folder, then selecting Check Out All from the File menu will check out all the files in that folder and descendant folders.
Also, note that clicking the All Descendants button will show all files in descendant folders as well as the selected folder.
Sounds like you might have checked out to a specific location. There is (or at least used to be) an option in the check-out dialog to override the location of the checkout, and in this case all of the files would be placed in that specific location. What you need to do in StarTeam is set your Alternate (not Default) Working Folder for the View, and then all of the files you check out will be put in the relative location based on the folder name. Do not override the working folders at the folder level, because this will cause your folder structure not to be mirrored. If you keep it simple and always set the Alternate Working Folder at the View and nowhere else, all your checkouts should go to the expected location. Don't override in the checkout dialog. Keep in mind, however, that even if you don't override the default working folders at the folder level, someone else on your team might. In those cases you can override their overrides by setting your alternate working folder to the folder name. This is one of the most painful and poorly designed aspects of StarTeam and always has been. Despite years and years of proposed enhancements to fix this, they have done nothing to address these issues. Be vigilant!
In P4V I can select a file, view its history, and use the options under the "show branch history" button to see changes made in other branches.
When I select a directory however, the "show branch history" button disappears. How do I view the history over different branches of all the files contained under a directory?
Probably easiest to use Revision Graph to do this. It'll let you follow the path of all of a folder's files back into other branches (can also do it recursively if there are subfolders).
Be warned: the output can get intense if there's a lot of other branches, and/or a lot of files. There's a filter on it so you can narrow down which files you care to look at though.
Over the last few months, I've been doing some maintenance on a project with many source files. I was recently informed that there is an issue with one of my bug-fixes and I was asked to fix my bug-fix.
However, since there are so many files and folders within the project, I can't remember which one I modified.
Therefore, I would like to be able to search within the root directory of the project for changesets that have affected files within the folder. I'm sure that I could determine which changeset caused the problem by the comments I put on them.
How can I find all TFS changesets that affect at least one file within a specific folder?
If you're interested in viewing the history for a single folder, navigate to that folder in Source Control Explorer, right-click on it and select "View History".
This will show you all the changesets that have affected this folder.
I frequently have to diff two trees of source files, one coming from svn (in which you can only check out the whole tree) and the other my eclipse workspace.
99% of the time I only want to see diffs in files that are in both compare trees. The svn side has thousands of files my workspace does not, and I don't need to see them.
Is there a way to get the compare utility to only show files that exist on both sides, and skip the ones it would put the little minus icon on?
One option would be to carefully select only the files and folders you want included in the comparison, then right-click and choose Team > Synchronize with Repository.
That will open the Synchronize perspective and show a Inbound/Outbound view of changes. From there you can "pin" the synchronization and later come back to it and re-sync to see updated results.
You can read some more about the Synchronize view at http://www.eclipse.org/subversive/documentation/teamSupport/workspace_synch.php
I have a project on codeplex and I'm trying to reorganise the tree structure so it makes a bit more sense and is easier to work with.
This is my current layout:
TopLevel
|-->src
|--->ProjectA //This is where all the files are held
|-->Core //plus three more folders
|-->MyProject.Core
|--->trunk
|-->src // I want to move all the folders and files in ProjectA into here
So I want to move all folders and files under ProjectA to ProjectA.Core/Trunk/src.
I checkout the whole source tree and right-clicked dragged the folders under ProjectA folder and selected "move versioned files here" into the src folder, that marked the folders in Project for deletion but the new files in src still had the green tick next to them and not the blue plus button.
After I commited the changes I had a look in the repo browser and saw that the folders hadn't been moved and were still in the ProjectA folder.
How can I move folders and the files in those folders to a different folder in subversion? Without loosing version history.
I'm using TortoiseSVN.
EDIT: Turns out it must have been codeplex, I moved my project to google code and everything works fine.
This type of reorganisation is easy to do with the Subversion command line client, which might be a viable option for you. Here's the commands that would do it (from the TopLevel directory):
svn mv src/ProjectA MyProject.Core/trunk/src/
svn ci -m "relocate ProjectA"
You can also combine both commands into one by using URLs as the source and destination, see the svn mv documentation for details.
I haven't found an easy way to do this sort of thing with TortoiseSVN, so when I need to I just use the command line client to do it.
I don't know what I was thinking when I suggested to export and import the files. I think I've been away from TortoiseSVN too long. I recall that tortoise svn actually has a really easy method of moving whole directories. It's not just obvious... but it's not clear why you can't get the result committed correctly to the repository. Presumably you did commit on the parent of all these folders.
Here's the summary:
You must select the folder and files you wish to move, and after doing so right click on the selection and drag it with the right button to the new location. You will get a context menu asking if you wish to relocate the files in the repository. This retains the history. Now your old files are marked for deletion and your new files should be marked as added. (I've found the status icons to be... not always representative of the true status). Commit this as one commit. I like to be picky and use check for modifications on the root of the checked out files, and then select exactly which changes I want to commit before doing so.
In the case of just moving one folder like this, open a window that is a parent to this folder, and another window that will be the new parent of this folder. Right click and drag all in one motion. I can't believe it takes this much text to describe a simple mouse action.
The standard strategy for dealing with nasty moves is, in the worst case, create all the new directories, move only the files from the old directories to the new directories, and then remove all of the old directories. This should get around almost any problem you encounter, and you can take shortcuts (moving entire directories and or trees) where that does work.
This will preserve history on all files. It will not preserve history on directory creations, but usually this is something you can live with, since you do have history for all of the file moves, which include the old and new directory names.