search

microsoft / azure-artifacts-migration

Migration scripts to help move your packages to Azure Artifacts from other package repositories.
MIT License
13 stars 18 forks source link

Support migrating off NuGet.Server #3

Open loic-sharma opened 4 years ago

loic-sharma commented 4 years ago

See https://github.com/NuGet/NuGetGallery/issues/5038#issuecomment-582026271

qJake commented 4 years ago

@loic-sharma Thanks for opening this issue for me! Looking forward to this.

I think, at a minimum, if there was an additional function in the module that worked with V2, that would satisfy the requirements, i.e. creating something like a Move-NuGetV2Packages.

chasewilson commented 4 years ago

Hi @loic-sharma, @qJake. Thank you both for the feedback. This would be a great addition to the module. In the mean time have you checked out the Move your packages to the cloud page? Is there something missing on that page for NuGet.Server?

qJake commented 4 years ago

@chasewilson In reviewing that page specifically, no, there's nothing inherently wrong there. In fact, that's what I ended up doing (copying our Nuget.Server's datastore locally, enumerating each package with PS and pushing the package up to Azure Artifacts). However this was a manual process (I had to write a bunch of PowerShell and handle edge cases like the version folder saying 2.7.0 but the package file name containing 2.7.0.0 so it trips up NuGet, for example).

I think what I was hoping for, is in this article:

https://docs.microsoft.com/en-us/azure/devops/artifacts/tutorials/migrate-packages?view=azure-devops

Having those PowerShell tools support the NuGet V2 API in addition to the NuGet V3 API.