I migrated a Team Project to a different collection using Microsoft Team Foundation Server Integration Tools.
Now I would like to take the original project offline (but not delete). Anyone knows of a way to do this?
Thanks
You should be able to accomplish this by removing all the users from the security groups of the original project.
Related
Are there any Team Foundation built-in services to help manage your project, team, access levels etc? I know there's a web front end but I have a requirement to bulk create projects and set them up.
There is a tool called the TFS Team Project Manager which sounds like it's what you're looking for.
http://teamprojectmanager.codeplex.com/
I have a project that is in the default collection on my TFS server. Is it possible to move the project from this collection to a new one that I created? Thank you
The project exists within the Collection Database, you can't just pickup and move a Team Project out of a database.
There is a TFS Integration Platform that can copy Team Projects between services.
Generally it's best to plan this sort of stuff upfront as to avoid issues like this down the line. I have heard rumours Microsoft are working on improving this, but I don't think anything will be available for a while.
Is there a way to access another Admin's Team Alerts in TFS 2010?
I don't have much experience using TFS other than checking code in/out. I was recently put in charge of changing around some team alerts that were previously created by another Admin. Is there a way for me to access the alerts he set up?
There are over 100 alerts which will be a pain if I have to remake them on my account. If anyone knows of an easier way such as exporting the alerts or transferring them I would appreciate it.
I suggest you to use Tfs Web Access, click on Settings at the top right corner, select Team project\Alerts
Other solution :
You can use the BisSubscribe tool commandline located on your tfs server in %ProgramFiles%\Microsoft Team Foundation Server 2010\Tools
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".
We're starting to user Team Foundation Server and my boss would like some way to "archive" projects. Meaning after they are completed, remove them from an "active" state so that only "active" projects are visible.
Does anyone have any experience with this?
I've thought of 2 options.
1) Create 2 base projects. 1 for active projects and 1 for achived projects
2) Remove all users from the archived projects.
Thanks,
Sam
I would personally recommend waiting for TFS 2010 when more functionality will be introduced that will assist you in the ability to "archive" Team Projects.
In TFS 2010 you will hopefully be able to move a team project to a new Team Project Collection. Actually you do this by duplicating your "active" project collection and then deleting all the team projects from it apart from the one that you want archived. In this active project collection, delete the archived project that you have a copy of in the duplicated project collection. This archived team project will then live in it's own project collection which means it has it's own database etc which can be easily backed up / archived etc.
The archived team project project collection can then be left as it is as it doesn't slow down the server any if not being used - or it could even be detached from the TFS Application instance so that it doesn't show up at all and re-attached at any time.
An advantage of using project collections in TFS 2010 is that full Version Control and Work Item Tracking history will be maintained.
I would use it just as you normally do, but when you are done with the project then you remove it from the visible list. (In Visual Studio you can right click on a project in the team explorer and say remove.)
If you are worried about changes after the project is done, then remove the users from the contributors list. If you really want to boot the users out (so they cannot even see it) then you can deny them rights to the project.
This way you don't have to see it, but you can keep all your projects on the base level.
I would NOT recommend having just 2 base project for active and in-active. A TFS project should not be based on a state.
We created an "Archive" team project and we regularly move unused source code to that team project. It has worked out well for us, the history is preserved so we can always reference the archive project for old code or information on past changes. We also limit access such that developers have read access but only TFS administrators have write access. I haven't checked to see how these moves impact the association of check-ins with work items - mostly because everything we archived was checked in before we moved to TFS.
As for the one active team project, I was led to believe by knowledge experts and online documentation that this wasn't the best way to organize team projects. I think ideally you group projects/solutions together into a single team project if they are related (i.e. by line of business or dependencies).
I'm sure you've already done your research, but there is plenty of documentation out there that might assist (especially if your team maintains a single application or a handful of applications). I would suggest starting with patterns & practices: Team Development with TFS.