Support

• B

  Unexpected URL for feed after creating with /api/management/feeds/create and endpointURL
  18 days ago • bill.hertzing_2810   16 days ago

  3
  0
  Votes
  3
  Posts
  18
  Views

  B 16 days ago

  Thank you. Your comments clarified a few things. I added useApiV3 = $True to the body above, and removed the incorrect use of endpointUrl. The big mistake in the above was Register-PSRepository - I needed to update Microsoft.PowerShell.PSResourceGet to the latest version, and use Register-PSResourceRepository -Name $feed.ShortName -Uri $endpointUrl -ApiVersion 'V3' -Trusted -passthru, where endpointUrl was http://<hostname>:50000/nuget/$feed.ShortName/ Problem solved, thanks again!
• 

  Drop Path not deleting
  28 days ago • steviecoaster   17 days ago

  3
  0
  Votes
  3
  Posts
  13
  Views

  17 days ago

  Late reply (was out at a conference), but this was in fact permissions related. I've added a check to ensure the Inedo service account has been granted modify permissions on the drop path upon creation, and it is working appropriately!
• P

  Unable to GET from connector "nuget.org"; using cached copy.
  1 May 2025, 04:14 • parthu.reddy   18 days ago

  10
  0
  Votes
  10
  Posts
  39
  Views

  18 days ago

  Hi @parthu-reddy , This looks more related to Server Overload / Database than anything to me. Note how all the requests are coming in at exact same second. Can you throttle your load balancer a bit, so they don't all hit at the same time? Even a slight delay will help. FYI - we are tracking a recent regression to SQL Server analysis engine (???) that is causing one particular query (NuGet_GetPackage) to go incredibly slow under extreme traffic. For some reason, it's using the wrong plan suddly. It's been happening to a few users after a recent upgrade/patch to SQL Server. We have a work-around but would like to test it in the field against a user. Thanks, Alana
• M

  Using LDAP on Buildmaster located in a container (Linux)
  23 days ago • marc.ledent_9164   18 days ago

  4
  0
  Votes
  4
  Posts
  15
  Views

  18 days ago

  Hi @marc-ledent_9164 , This is available in InedoCore-3.0.4, so if you go to Admin > Extensions, you should be bale to update. thanks, Alana
• 

  Proget - Migration of Legacy Debian feed to "normal" Debian feed is broken
  23 days ago • inedo_1308   21 days ago

  3
  0
  Votes
  3
  Posts
  10
  Views

  21 days ago

  Many thanks, Alana! I can confirm, that the proget:24.0.37-ci.2 container image works like a charm Thanks for the quick fix! Fritz
• M

  Error when attempting to connect BuildMaster to Bitbucket Cloud
  24 days ago • mhelp_5176   23 days ago

  4
  0
  Votes
  4
  Posts
  14
  Views

  23 days ago

  Hi @mhelp_5176 , I haven't investigated BitBucket Cloud any further, but it sounds like there's an issue with the integration -- and it's definitely something we can look at later. My guess is that it's some kind of change to the API/authentication. But we're all pretty focused on getting ProGet 2025 out the door, so it'll have to be after that. That said, the main difference between connecting to a "Git host" like GitHub, GitLab, Gitea, BitBucket, etc. vs a "generic Git repository" is that there will be some intelligent drop downs to help you select a repository. There are a few other differences as well, but mostly it's UI. So for example, on a GitHub connection, you'll see a list of organizations and repositories, and then would select the one to connect to. Compare this to the "Generic Git repository", where you simply paste in the repository clone url. But in either case, you need to configure each repository connection individually; typically each application will have one repository, which is why this is part of the application creation process. It's definitely not a common practice to be able to "pull in all the repositories in a workspace" at once - that's not really how Git works, and it would involve some kind of script that iterates a list of repositories and clones/updates each one indivdiaully based on configured remotes in subfolder., Cheers, Alana
• K

  Aggregating 2 Feeds in ProGet Free Edition
  21 Jan 2025, 10:55 • kc_2466   23 days ago

  20
  0
  Votes
  20
  Posts
  71
  Views

  K 23 days ago

  I've now found a cleaner way of adding this entry to the host file... If using docker run, add the argument: --add-host=<host_server_name>=127.0.0.1 if using a docker compose file, add an entry: extra_hosts: - "<host_server_name>: 127.0.0.1"
• S

  ProGet apt add pgp key
  6 May 2025, 08:30 • stefan.hakansson_8938   28 days ago

  3
  0
  Votes
  3
  Posts
  11
  Views

  S 28 days ago

  Great, thanks!
• 

  Unable to list feeds with pgutil
  29 days ago • steviecoaster   29 days ago

  2
  0
  Votes
  2
  Posts
  5
  Views

  No one has replied

• 

  Programmatically License ProGet
  14 May 2025, 14:51 • steviecoaster   30 days ago

  2
  0
  Votes
  2
  Posts
  15
  Views

  30 days ago

  Hi @steviecoaster , You can use pgutil for this: pgutil settings set --name=Licensing.Key --value=XXXXXX This is in the Configuration table FYI, which is what pgutil settings does Thanks, Steve
• M

  Pull Maven artifacts - invalid version
  8 May 2025, 09:42 • michal.roszak_0767   14 May 2025, 14:28

  19
  0
  Votes
  19
  Posts
  37
  Views

  14 May 2025, 14:28

  @michal-roszak_0767 said in Pull Maven artifacts - invalid version: Next victim: https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/ jeeze, what a mess! Well, there goes any hope of using v[0-9]+ -- they just straight up use random strings as version numbers. https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/. https://repo1.maven.org/maven2/org/springframework/data/spring-data-releasetrain/Neumann-SR9/ Open to ideas, but based on the URLs alone... I don't see a good way to identify one of these as an artifact and the other as a version of an artifact.
• M

  ProGet - proxy to RAW Repository
  14 May 2025, 09:12 • michal.roszak_0767   14 May 2025, 10:44

  8
  0
  Votes
  8
  Posts
  8
  Views

  14 May 2025, 10:44

  @michal-roszak_0767 it wouldn't hurt to start a new topic about it, but it's design decision so you'd have to make a good use case for it :) I can't find the discussion (maybe it was internal), but the idea is that "generic website connectors" for Asset Directories are a poor solution for "offline" environments. A "generic proxy" like ngnix will always be better in every way.
• D

  NuGet package has no symbols - No symbols in this package have been indexed.
  13 May 2025, 14:06 • ds_6782   13 May 2025, 15:02

  3
  0
  Votes
  3
  Posts
  6
  Views

  D 13 May 2025, 15:02

  Hi Steve Thanks for your response. I've read the documentation and for the client part I followed the Microsoft documentation: https://learn.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg After some testing, I've found the problem: I had to add /v3/index.json to the URL. Now the package and the symbols are pushed to the server. The ProGet UI shows the correct URL under API endpoint URL:. I'm not sure why my build script was using the URL without v3. Maybe it was different in an older version of ProGet or I just made a mistake somewhere? Interesting is that pushing "worked" when using the URL without v3 and v2 API disabled for the feed. Maybe the client NuGet client contains some logic to only push the snupkg file when it detects a v3 source?
• D

  nuget search not working with api v2 disabled
  13 May 2025, 13:51 • ds_6782   13 May 2025, 14:29

  3
  0
  Votes
  3
  Posts
  6
  Views

  D 13 May 2025, 14:29

  Hi Steve Thanks for your answer. I saw this in the doc and thought it will use v3 https://learn.microsoft.com/en-us/nuget/api/search-query-service-resource It is possible to search for packages available on a package source using the V3 API. The resource used for searching is the SearchQueryService resource found in the service index. In this case, sorry for the question and please forget it^^
• E

  Conda feeds: some packages not visible in WebGUI
  4 Feb 2025, 10:50 • e.rotteveel_1850   13 May 2025, 08:51

  5
  0
  Votes
  5
  Posts
  16
  Views

  13 May 2025, 08:51

  Hi @e-rotteveel_1850 , Just as an FYI, this was much more complex that it seemed, and we ended up creating a whole new feature to address this called Feed Integrity Checks. This will shipped in friday's maintenance release, and in theory should spot and allow you to resolve the issues:https://docs.inedo.com/docs/proget/feeds/feed-overview/proget-feed-storage#feed-integrity-checks Alex
• S

  TCP Agent configuration
  buildmaster • 12 May 2025, 10:33 • sergio.gonzalez_0157   12 May 2025, 15:24

  2
  0
  Votes
  2
  Posts
  17
  Views

  12 May 2025, 15:24

  Hi @sergio-gonzalez_0157 , Typically, Deployment Targeting is done in the Pipeline: https://docs.inedo.com/docs/buildmaster/deployment-continuous-delivery/buildmaster-pipelines#deployment-targets This way, you don't need to put for server or anything in your script. So, my guess is that your Pipeline is actually targeting the ProductionServer (but not running anything on it, except intializing the agent), but your script is targeting the BuildMasterServer. -- Dean
• U

  ssl certificate does not work
  24 Apr 2025, 16:37 • udi.moshe_0021   9 May 2025, 15:16

  16
  0
  Votes
  16
  Posts
  41
  Views

  9 May 2025, 15:16

  Ah, that makes more sense! Yeah, Github is weird like that. I think if I provided the raw link then that right-click would have worked. Sorry for the confusion!
• M

  Proxy Group Problem
  9 May 2025, 07:37 • michal.roszak_0767   9 May 2025, 09:59

  2
  0
  Votes
  2
  Posts
  6
  Views

  9 May 2025, 09:59

  Hi @michal-roszak_0767, Oh that's a whole lot of connectors and this is most definitely going to cause some performance issues. Remember that ProGet needs to forward every request you make to all 10 of those servers, and some of these repositories will not respond very quickly. Like JCenter was deprecated/retired a few years ago, and I can't imagine is performant at all. Especially for things like metadata requests. Maven is not a very patient client and will time out while waiting for ProGet. There is really no way around this. You'll need to use less connectors. -- Dean
• M

  ProGet - Versioning restrictions
  8 May 2025, 09:14 • michal.roszak_0767   9 May 2025, 07:37

  6
  0
  Votes
  6
  Posts
  16
  Views

  9 May 2025, 07:37

  @michal-roszak_0767 those are also invalid versions and you should never upload them to a feed (repository) directly; see https://docs.inedo.com/docs/proget/feeds/maven#snapshot-versions The code has already been fixed and the maintenance release is scheduled for next week. We could get you a prerelease, but I don't think your developers are manually uploading artifacts using the Web UI? If you want to upload artifacts with bad versions now you can just use the maven client (e.g. maven-deploy) or just do a basic PUT of the file to the desired group/artifact-id.
• 

  Extending the migrator utility
  7 May 2025, 16:12 • steviecoaster   7 May 2025, 19:23

  3
  0
  Votes
  3
  Posts
  8
  Views

  7 May 2025, 19:23

  Thanks @dean-houston! That's good enough for me. Looking forward to trying the new migrator once it lands, sounds really really good!