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!

    Azure feed not syncing with ProGet

    Scheduled Pinned Locked Moved Support
    6 Posts 2 Posters 19 Views 1 Watching
    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.
    • C Offline
      cstekelenburg_4169
      last edited by

      I have setup Azure artifact feeds that should sync up to proget through a connector. I use a PAT from a DevOps account as authentication and have seen this work in a PoC we setup a while ago. Somehow I cannot get this to work on a fresh install at the moment. The connector is setup to connect to https://pkgs.dev.azure.com/companyname/Projectname/_packaging/Repositoryname/nuget/v3/index.json and I have enabled both Nuget API v2 and V3 on the ProGet feed. There are currently no errors to give me any kind of direction to go in.

      Does anyone have an idea as to what I am missing here?

      dean-houstonD 1 Reply Last reply Reply Quote 0
      • dean-houstonD Offline
        dean-houston inedo-engineer @cstekelenburg_4169
        last edited by

        Hi @cstekelenburg_4169 ,

        ProGet does not "sync" remote repositories, but instead displays and caches results through a "connector" you configure. If there are any connector errors, they will be logged when you do a query.

        Azure artifacts do not support searching or listing packages, so you won't "see" a package unless you type in the exact package name.

        -- Dean

        C 1 Reply Last reply Reply Quote 0
        • C Offline
          cstekelenburg_4169 @dean-houston
          last edited by

          @dean-houston Sync or cache, whatever it is, packages are not showing in proget at all. We have had a PoC that worked the way we expected it to work, pointed the connector to the azure artifact feed -> packages show up in proget, we pull/approve them and can install them through proget on an endpoint. That's the idea, but I can't get it to work now, and there are still no errors within proget at the moment. So what am I missing?

          1 Reply Last reply Reply Quote 0
          • dean-houstonD Offline
            dean-houston inedo-engineer
            last edited by

            Hi @cstekelenburg_4169,

            Azure Artifacts does not support the NuGet Search API, so this means you won't see packages on the feed/search page in ProGet. This is expected behavior with rudimentary NuGet repositories that don't support listing/searching.

            In the past, I'm guessing that you either:

            • used the Azure Feed Import Wizard, which will perform a one-time download using a special (non-NuGet API)
            • pulled packages via the NuGet API (e.g. with nuget.exe, visual studio, etc), which will then would cache them in ProGet

            -- Dean

            1 Reply Last reply Reply Quote 0
            • C Offline
              cstekelenburg_4169
              last edited by

              Unfortunately I cannot check how it was done in our PoC at this time, but let me rephrase the question: We have a DevOps repository with azure artifact feeds, how would I configure proget to keep the proget feed in "sync" with the artifact feed as that will be the source for new and updated for proget?

              I have tried a connector, but for some reason I'm still not getting results, but also not seeing errors.

              dean-houstonD 1 Reply Last reply Reply Quote 0
              • dean-houstonD Offline
                dean-houston inedo-engineer @cstekelenburg_4169
                last edited by

                Hi @cstekelenburg_4169 ,

                If you created a connector with the proper URL, username, and password, then you've set it up correctly.

                Please note, you will not be able to list or search remote packages in the ProGet UI. This is a limitation, since ADO is rudimentary and does not support listing/searching.

                Instead, you will need to use the NuGet API (Visual Studio, Nuget.exe) to pull packages. Once package has been pulled through ProGet, you will "see it" in the UI since it's been cached.

                I'm not trying to be pedantic with terminology, but please note it's not a "sync" -- it's more of a "proxy" or "pass through". When you make a request via the NuGet API, that API request is forwarded to your connector (I.e. Azure DevOps).

                -- Dean

                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