search

nkdAgility / azure-devops-migration-tools

Azure DevOps Migration Tools allow you to migrate Teams, Backlogs, Work Items, Tasks, Test Cases, and Plans & Suits from one Project to another in Azure DevOps / TFS both within the same Organisation, and between Organisations.
https://nkdagility.com/learn/azure-devops-migration-tools/
GNU Affero General Public License v3.0
503 stars 339 forks source link

Migration of Attachments doesn't work for VSTS #24

Closed chrisprinz closed 7 years ago

chrisprinz commented 7 years ago

During my migration-project from VSTS->VSTS, I faced the problem, that attachments are not migrated succesfully. I enabled the "Attachment-Processors" and according to my understanding of the log file, all attachments have been detected and moved correctly. Unfourtunateley in the target-projects all attachments have 14KByte and are unreadable. This happened with all files, independ from the file format.

I added the configuration for my productive-migration and a log from a test-migration. Please let me know, if I should provide more information.

Config.json.txt example.log.txt

MrHinsh commented 7 years ago

I have not seen this before and have done many migrations of attachments to VSTS. Recently I have seen 0kb as the size but the file is fine...

visma-theothustrup commented 7 years ago

I have just migrated TFS(local)->VSTS without this attachment problem. I have migrated txt, doc and pdf files. Maybe you can check out the export folder in the tool, to see if the problem is in export step or in the import step

manutsss commented 7 years ago

Hello, i'm testing this tool and also have detected this issue after migrating from VSTS to another VSTS. The problem is related with the Export Migrator, after setting up the config file with the AttachementExportMigratorConfig enabled, the downloaded file is corrupted and after debugging i think that the problem is related with the code line webClient.DownloadFile(wia.Uri, fpath); No exception is detected but this is not working.

bfbatch commented 5 years ago

I'm seeing a different issue with attachments. The export works, however most of the files are in .json format. Only a few are .png or the like. On the import, they are all skipped except the one. The one interesting thing is all the WIT IDs change, could ot be it can't fine the work item because of that?

TfsQueryContext: TfsQueryContext: TeamProjectCollection: https://dev.azure.com// TfsQueryContext: TfsQueryContext: idToFind: 91181 TfsQueryContext: TfsQueryContext: TeamProject: migration.exe Information: 0 : Query Complete: found 0 work items in 243ms 5 of 402 - Skipping 91181#SoftwareUnitTests.pdf to 0 TfsQueryContext: TfsQueryContext: TeamProjectCollection: https://dev.azure.com// TfsQueryContext: TfsQueryContext: idToFind: 91195 TfsQueryContext: TfsQueryContext: TeamProject: migration.exe Information: 0 : Query Complete: found 0 work items in 336ms 4 of 402 - Skipping 91195#SoftwareOrganization.pdf to 0 TfsQueryContext: TfsQueryContext: TeamProjectCollection: https://dev.azure.com// TfsQueryContext: TfsQueryContext: idToFind: 91195 TfsQueryContext: TfsQueryContext: TeamProject: migration.exe Information: 0 : Query Complete: found 0 work items in 127ms 3 of 402 - Skipping 91195#SoftwareUnitTests.pdf to 0 TfsQueryContext: TfsQueryContext: TeamProjectCollection: https://dev.azure.com// TfsQueryContext: TfsQueryContext: idToFind: 91672 TfsQueryContext: TfsQueryContext: TeamProject: migration.exe Information: 0 : Query Complete: found 0 work items in 122ms 2 of 402 - Skipping 91672#ReposToArchiveMove.png to 0 IMPORT DONE in 0 hours 0 minutes 55:776 seconds - 402 Files, 1 Files imported, 0 Failures, 401 Skipped

Attachment Export SessionID - 976a17c8-b107-4c4c-a681-4161e8fe1207

Attachment Import SessionID - db77c7f1-be41-4df9-a195-316503d51cdb