We are in the process of migrating from TFS 2013 to TFS 2017 and for most parts it went really well.
We took a copy of the VM, reinstated it under another server name. I then ran the upgrade over the test server and followed all the prompts, and noted that this was a test machine. So it changes the configs etc, as it needs to.
We then ran into issues. It seems as though it did not upgrade the work item templates properly. Has anyone gone through the migration and had similar issues? Also more importantly how did you solve it.
There are two things that don't quite work. They are the Testing module and reporting. I suspect because there are some work items that are missing.
It appears that the tests were not migrated (although I believe they are in the database). It may just be that they are just not appearing because the WIT are not defined properly.
Can someone please tell me what we can do to migrate the tests across?
Error that we get when trying to add a new test plan
Seems you are just missing the test plan and test suit. You could go through this topic -- Update a team project manually to support test management
This topic applies to a team project that is defined on an on-premises
Team Foundation Server (TFS)and was created using a process template
that doesn't have test plans and test suites work item types.
Related
I'm using TFS 2015 on-prem and I'm using the standard SCRUM template. I have 1 Team Project and I'm using the team field to segregate work. I have created a few build definitions and ran a few builds over the last few weeks.
When I installed TFS I did not install or configure Reporting Services straight away as I had planned to do that later. I have since done this and I now have my Tfs_Warehouse which is updating with most things but NOT FactBuildProject or FactBuildDetails. Some of my other facts are pulling over, such as FactCurrentWorkItem and even FactBuildCoverage. I have rebuilt the warehouse in the TFS Admin Console.
As this is a standard process template and standard reports I expect that the required fields should be set to reportable.
How can I get data in my FactBuildProject table and where can I look for issues with it? I'm not sure where to start and I can't find anyone else in the world with a similar problem.
If you are using the new task-based build system, then you are out of luck, since that data is not being propagated to the data warehouse.
Check the comments on this blogpost: http://nakedalm.com/create-a-build-vnext-build-definition-on-vso/
Some projects we're working on are hosted on a TFS on visualstudio.com. However, the owner is an early adopter account that will expire soon. We already have another TFS in place (also on visualstudio.com), and now we want to migrate the code and version history from TFService A to TFService B.
I've tried using the TFS Integration Tool (http://tfsintegration.codeplex.com/) and created a configuration to migrate between the two subdomains on visualstudio.com. However, despite the tool indicating succesful migration, nothing actually changes on the destination server. I've found this question on SO:
How to copy a team project from one collection to another with TFS Integration Platform, TFS2012 to TFS2012
I have basically the same issue as the OP, but the answer does not work for me. What can I do?
Last week I upgraded our TFS 2012 Server to TFS 2013. I read the MSDN documentation first and I also followed the documentation as I performed the upgrade. Everything seemed to go ok.
After the upgrade I ended up with 7 or so Team Projects that the wizard couldn't configure, for whatever reason, and needed manual configuration.
I noticed this week that ALL of the work items under one of my Team Projects are missing. Gone. Like even if I select Team|Go To Work Item and enter in a known Work Item Id, I receive an error that the item is either missing or I do not have permission to view it. I'm an Administrator on the TFS server and I'm the TFS Admin, so I highly doubt permissions are the issue.
I remoted into the server and launched SSMS to explore the raw data. I know for a fact Work Item 450 is missing (it's the only Id I remember at this point). I selected the TOP 1000 from WorkItemsAre, which seems to be the table that holds the Work Items (?). There is a gap in the Ids, I see 1-448, then the numbering picks up again at 457. So, somehow my Work Items appear to have been deleted. I stopped there, I assume there are more gaps since I'm missing more than 9 items.
Now I haven't gone through every one of our Team Projects. I've only touched 3 of them since the upgrade. Thankfully the largest, most active Team Project, with the most work items/version history seems to be intact. I'm not sure if any other Team Projects are missing their Work Items too.
Has anyone else experienced this? Does anyone know if there's some "secret squirrel" way to recover these missing work items, or have they been hard deleted and are gone for good (other than looking through tape backups of the server).
Any advice would be appreciated.
I already migrated to TFS 2013 from TFS 2012.
The problem of manual configuring the project may occur when you have customized work item types in TFS Project Templates. Did you customize your project templates?
Although, I can hardly believe that work-items getting hard deleted from TFS. This issue may occur probably because of archiving during migration. The workitems that TFS upgrade wizard may not have "understood" during migration/upgrade, might be archived and moved to another table in database Tfs_DefaultCollection.
You may want to consider that. I am not sure if that may be the case, but this happened when we migrated from TFS 2010 to TFS 2012 because we had many custom work items in TFS 2010. Hence we had to standardize templates before migration using powershell. But we lost some amount of history.
Hope that sparks some idea.
We're running TFS 2008 SP1, which has been upgraded all way from TFS 2005 Beta.
Since the old 2005 days we've had this project, lets call it Project A, that we now want to get rid of/destroy. However, this certain folders from this project have been branched off onto another project, Project B, that's currently in use and we definitely don't want to impact it.
So my question is, if we destroy Project A can it have a domino effect and destroy stuff in Project B or have any other adverse affect that we might not have considered?
I've done some testing in test environments for this and it seems to be fine but since we have no users in the test environment I thought it would a good idea to check with the experts out there before we do this in Production!
Also, is there any way of getting a fairly accurate or just a ball-park figure of the size of a Team Project within TFS 2008 ?
Thanks
We also have a database from the "beginning of time". I haven't seen any domino effects when doing that, but do have the sql and tfs patches in order for e.g. the "destroy isn't executed in transaction bug".
I have installed and configured TFS 2010 on a Win 2008 server. I have tested the migration and everything seems o be working fine. I have one issue with the Domain move though.
I am trying to use TFSCONFIG IDENITIES /change command to map the Users in old domain to new domian, but unfortunately the new domain accounts have been added to the TFS group. Hence, I caanott use the Identities /change command.
I am still trying to figure out what needs to be done in order to sync up the accounts b/w two domains. What are my options in this situation? Can I just uninstall and re-install TFS 2010. Would that help me sync up the account names b/w two domains? Please advise
There is extensive guidance available on the different supported upgrade scenario's.
Probably the easiest way to do the upgrade is to install TFS2010 over the 2008 version and then do a domain migration. It looks like the issue you're facing is that you added the new account members, instead of migrated the old members to the new ones. I haven't been in that scenario before, you could try removing the new accounts and then migrating, or using the TFS integration tools to migrate all data for one user to another user.
If you still have a backup available, or if the TFS 2008 server is still there, I suggest re-doing the migration, however painful that may be, it will be the safest way to get everything to work again.
Finally there are the The TFS Integration Tools can be used to migrate from one TFS instance to another, they don't migrate everything, but will migrate the most important things.