Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. richards_8960
    R
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    richards_8960

    @richards_8960

    0
    Reputation
    4
    Posts
    1
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    richards_8960 Follow

    Best posts made by richards_8960

    This user hasn't posted anything yet.

    Latest posts made by richards_8960

    • RE: Understanding the API for NuGet Packages

      Thanks John.

      We have tried the FindPackagesById endpoint and this is completing in 75ms which is much more expected. We are going to continue with this API to see if we can get what we need from it.

      posted in Support
      R
      richards_8960
    • RE: Understanding the API for NuGet Packages

      So having done some digging around database procs it appears all our packages are part of the NuGetPackageVersionsV2_Extended view not NuGetPackageVersions_Extended.

      We had assumed that the NuGetPackageVersions_Extended was the default "v3" protocol and the "V2" api was legacy.

      As far as we can tell, and assume, ProGet doesn't yet support the v3 NuGet protocol. Can you confirm?

      posted in Support
      R
      richards_8960
    • RE: Understanding the API for NuGet Packages

      For the Database stored procedure, is there a code repo we can look at - or just do an inspection on a running instance?

      For the NuGet API, we don't have any connectors configured on ProGet. By connector, I am assuming that when I go from the Feeds screen to the Connectors tab it displays:
      There are no connectors that match the specified criteria.

      Our instance is running 733 packages with 34000 versions. Does this play a part as well?

      posted in Support
      R
      richards_8960
    • Understanding the API for NuGet Packages

      We are attempting to use the ProGet API for a NuGet feed, but we are not having much luck with understanding what parameters to use. Our goal is to be able to query into ProGet and get the latest pre-release package and then create an Octopus deploy with the versions found.

      We thought we could just use the endpoint:

      https://<server>/api/json/NuGetPackages_GetPackages?API_Key=<key>&Feed_Id=1&PackageIds_Psv ="Scripts"
      

      where Scripts is the name of the package. However, this returns:

      []
      

      So we tried NuGetPackages_GetPackageCount but always get a count of 0. So we tried:

      https://<server>/api/json/NuGetPackages_GetPackage?API_Key=<key>&Feed_Id=1&Package_Id=Scripts&Version_Text=2.60.0.1492-green
      

      And got:

      {
          "NuGetPackages_Extended": [],
          "NuGetPackageSymbols": []
      }
      

      If we use the OData API:

      https://<server>/nuget/halo/Packages()?$format=json&$filter=Id eq 'Scripts'&$top=1
      

      We can find the package, but this query take 11s+ to return, and we would need to do 70+ queries, so we are trying the JSON API.

      At this point we have no idea what to pass to the server for Package_Id, Version_Text or PackageIds_Psv.

      Is there any help for what to use for the fields in the API?


      ProGet Version : Version 5.2.23 (Build 7)

      posted in Support
      R
      richards_8960