Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Bulk import is not working

    Scheduled Pinned Locked Moved Support
    proget
    5 Posts 2 Posters 48 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      I created a folder on proget's server and placed all legacy's nuget packages in it to do a bulk import in to Proget.
      i set the Bulk Import Drop Path on a specific feed.
      But Proget does not import any packages to the feed.

      i think the permission is ok.
      if you need any other information, you can send a email to me.
      i can attach the inform you want.

      Product: ProGet
      Version: 4.0.8

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Please ensure that the service is running, and that the service has permission to read and delete files from the feed.

        Note that sub-directories are not supported, only the packages themselves.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          How can this be considered a bulk import if subdirectories are not supported? I couldn't figure out why this wasn't working until I found this post. I copied an existing nuget packages folder and just couldn't figure out why nothing was being imported. So, if they are only imported from the root, I have to copy in one package. Wait for pickup, then copy in the next package? That seems very strange. The other option is to find some tool or command line that will copy all of the files into one folder, but then that runs the risk of file collisions. I'm just really stumped as to how this can be considered a bulk import method, pleas help me out... how do I do things in bulk?

          1 Reply Last reply Reply Quote 0
          • benB Offline
            ben inedo-engineer
            last edited by

            Here's a PowerShell (File → Open Windows PowerShell) script that will move all the files to the root of the drop path:

            Get-ChildItem -Recurse -File | ForEach-Object {Move-Item $_.FullName .}
            

            Make sure you run that inside your drop path, because it could do damage somewhere else.

            1 Reply Last reply Reply Quote 0
            • ? This user is from outside of this forum
              Guest
              last edited by

              I'm pretty sure mike you don't need to copy the folders one at a time and wait for pickup...you could copy all the packages at once.

              And watch out for that powershell script -- it will copy all files in all subdirectories into the current directory, so if your subdirectories contain things other than packages you should add a filter to it.

              1 Reply Last reply Reply Quote 0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              • 1 / 1
              • First post
                Last post
              Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation