We have a TFS 2013 on-premises server that we just migrated over from VSO for a customer. They originally had 2 VSO accounts. Each account had a collection of projects. They have now been attached to the TFS thereby creating 2 collections that we can see & browse successfully. They'd like to merge all of the projects into one collection while maintaining all history info, etc... Is this possible? We are NOT trying to merge projects...ONLY the collections.
The process for merging Collections is exactly the same as the process for merging Team Projects. You would pick one collection to keep and create a new Team Project for each of the Team Project that you want to migrate from the other collection. You would then use the TFS Integration Platform to push the data across...
I know this is not what you want to hear but it is the only possible way to achieve this.
Related
I am new to Team Foundation server.
1)What is meant by collection in TFS?
2)How can me and my friends work on a project using TFS?
1)What is meant by collection in TFS?
Simply saying a team project collection is a group of team projects in TFS.
When your Team Foundation Server (TFS) hosts multiple team projects, you can manage them more efficiently by grouping them together and assigning the same resources to them. For example, you can group projects that have similar requirements or objectives, such as all team projects that access a particular code base. You can then manage the group of team projects as an autonomous resource with its own user groups, server resources, and maintenance schedule.
A group of team projects is called a team project collection. When you install TFS, a default collection is created to contain all team projects. When you create a collection, you specify the logical and physical resources that team projects within that collection can use. All the artifacts and data that those team projects use are stored in the single database of the collection.
See Manage team project collections in Team Foundation Server for details.
2)How can me and my friends work on a project using TFS?
Too much content for this question. Suggest you reading the Quickstarts documents first.
Basically you need to do following things first:
Create a team project
Add users to a team project or specific team
Add administrators, set permissions at the project-level or project
collection-level
Connect to TFS --> Version Control --> Build/Release
Please refer to the Guide link for each related point : https://learn.microsoft.com/en-us/vsts/?view=vsts#pivot=start
Also here is a simple guide for your reference to Get Started with Team Foundation Server 2015
I'm trying to migrate my existing code to TFS 2013 Express.
I have single Team Project Collection and inside it 3 team projects:
-web
-winforms
-wpf
If I add project web-project1 (solution) to team project (for example to web) and check in I get info that change set 1 was saved.
If I add another project (winforms-project1) to other team project (winforms) and check in I get info that changeset 2 was saved.
If I return to first project (web-project1), change something and check in I get information that changeset 3 was saved, but this is my second commit to that project.
Can I configure TFS to have changeset incrementation counter for individual projects instead of one global counter for Team Project Collection?
No, TFS changesets exist across the whole TeamCollection, so are shared amongst TeamProjects.
This allows you to copy and move projects with history and changeset info across TeamProject boundaries.
In your specific example, creating a Web & Winforms TeamProject sounds like you are going about it the wrong way and are starting off at too high a level.
Surely your UI projects could share Business Logic code? Therefore, they should belong in one TeamProject.
Is there any way to move/migrate team projects of a Team project collection from one TFS server to another (both in TFS 2010 version). The destination Team Project collection contains a Team Project already and I want to move the source Team projects in to this particular team projects. So at the end I will have a Team Project which contains several projects in it. Is that possible? I want the history to be preserved as well.
If the above scenario is not possible, can I migrate Team projects from one server to another without going through the database backup-restore-TFS detach-attach process?
I thought of trying the TFSIntegration tool, but could see many people advised to avoid using this due to issues in it.
So if you have any information in accomplishing this, that would be great..
If you want all the history then you really only have 2 options:
TFS Integration platform - http://tfsintegration.codeplex.com/
Back up /restore the collection database - http://msdn.microsoft.com/en-us/library/dd936138.aspx#Backup
I would recommend moving the database. This sounds pretty onerous but is actually quite easy.
Good Luck!
TFS INTEGRATION PLATFORM used for integration.
A tool which helps a lot named "witAdminUi".
I need to create a new project from an existing one in TFS. This is for source control only. I do not need to copy any work items.
so now i need to create NewTeamProject in NewProjectCollection and use the source branch of OldTeamProject in OldProjectCollection.
Kindly advise to go ahead with this.. Thanks a lot for your help in advance..
Manual Split
Create a new team project in your existing collection
Pick the branch from team project option in the creation wizard
Follow the split a team project collection guidance
However, I have a feeling that this will not bring all the history along with it, and it's not a particularly nice option, especially when it comes to the collection splitting.
TFS Integration Tools
Another way is to use the tfs integration platform, which basically replays all the checkins on a new team project, which can be in your new collection. You will lose the original date/time of the checkin, due to the way this program works but will still be able to see what each checkin changed.
TFS Integration Tools
Tfs integration tools blog posts and references
There is one risky way to get your timestamps correct, by manually updating the database
We have a Team System environment where our applications are set-up as separate Team Projects. Often, we run into a scenario where a development task requires updates to code in multiple Team Projects.
In this scenario, what are the pros/cons to having a single changeset that contains coding changes across multiple Team Projects? What are the pros/cons to using a one-changeset-per-Team-Project approach?
Providing the changes are made within a single workspace and all the team projects are in the same project collection (this applies to TFS2010) then a single checkin can span multiple team projects.
Within a single server (TFS2005/2008) or team collection (TFS2010) there is a single version control repository with the team projects defining the root folders: all version control operations can span different team projects.
I see no problem with this approach. Remember that TFS will allow you to rollback to the previous changeset, or inspect the files affected by a changeset (comparing to previous versions) so you can rollback some or all of your changes if required.