Group Details Private

administrators

  • RE: Add custom tags to nuget packages

    @forbzie22_0253,

    From an API standpoint, I believe only npm packages support server-side tags. Rubygems might, but in any case we strongly advise against using them: https://blog.inedo.com/npm/smarter-npm-versioning-with-semver/

    Server-side tagging is not likely something we will support in the future. Deprecation and Listing are really only there because many of the client APIs support them.

    I'd need to see a strong, specific use case. If it's related to quality (e.g. dev, staging, prod), then it's a "hard no" because our solution to quality is prerelease version numbering/tagging with repackaging.

    I do know that Sonatype Nexus has always supported tagging, but their repository is more of a "fileserver with server-side metadata" and ProGet is package-based. The only documented use case they have for tags has been quality, and our solution/approach is far superior.

    Cheers,
    Alex

    posted in Support
  • RE: Performance Issues after upgrading ProGet to v2024.16 from v6.0.20

    @sneh-patel_0294 and as an FYI, if you haven't already, you can request a ProGet Trial key from My.Inedo.com, and then set it to ProGet Enterprise, which supports the Clustered installation

    posted in Support
  • RE: Performance Issues after upgrading ProGet to v2024.16 from v6.0.20

    Hi @sneh-patel_0294 ,

    A "chained connector" would be something like, "(Feed A) --> (Feed B) --> (Feed C)". We've seen some set-ups like "(Feed A) -> ((Feed B) + (Feed C --> Feed F)+ (Feed D --> Feed G))", and every now and then a "loop" (where Feed A eventually connects back to Feed A). Those are really bad for performance, especially with NuGet v2 which requires a query every every single connector.

    As for a clustered installation, here's our set-up guide for that:
    https://docs.inedo.com/docs/installation/high-availability-load-balancing/high-availability-load-balancing

    But to answer your questions... a sstandard share drive and a common SQL Server is fine. The main thing is to spread the incoming network traffic across multiple web nodes.

    Cheers,
    Alana

    posted in Support
  • RE: Performance Issues after upgrading ProGet to v2024.16 from v6.0.20

    Hi @sneh-patel_0294 ,

    The underlying issue is that you ProGet server is getting overloaded, and you need to find a way to reduce peak traffic or switch to a load-balanced solution. Removing NuGet V2 APIS, chained connectors, etc. are a good step in reducing traffic.

    Keep in mind that the clients (build servers, dev workstations) are sending 1000's of simultaneous requests to ProGet at one time. ProGet is not a static file server (unlike nuget.org), and each request must be authenticated and often proxied/forwarded to connectors. There is only one network card on the server, and this is what happens when it gets overloaded.

    As for why it's causing errors now, this is a result of changes to the underlying platform (.NET Framework to .NET Core). The older platform did a better job of throttling traffic under extreme load and, for whatever reason, didn't timeout as much.

    You can configure a throttle in ProGet by going to Admin > HTTP/S Settings > Web Server > "edit", and then set a value of 100 or so. You mentioned a value of "500", but I would just set it to 100.

    Cheers,
    Alana

    posted in Support
  • RE: Many timeouts in ProGet log when restoring packages

    Hi @enrico-proget_8830 ,

    Using ngnix is probably a better solution anyway if you don't mind setting that...
    but the setting is now under Admin > HTTP Settings > Web Server " Edit"

    Thanks,
    Alana

    posted in Support
  • RE: Proget: Debian2 connector to https://packages.microsoft.com/ubuntu/22.04/prod/ results in unique constraint failed error

    Hi @it4it_9320,

    That's about the size I'd expect for a connector to that index. So far, I can't get it to grow much beyond that - I'm wondering if this was caused by the transaction rollback after the constraint error happening over and over. In any case, we'll add an explicit VACCUUM after major updates that ought to prevent the index from expanding again.

    -Greg

    posted in Support
  • RE: Ubuntu 24.04.1 InRelease Problem

    Hi @udi-moshe_0021 ,

    I don't know... as I mentioned, when we follow our instructions to set up a Debian feed in ProGet with a connector to http://ftp.debian.org/debian/ (Buster) it seemed to work fine. Other users seem to have no issues with the steps there, which is why it's likely your network.

    Beyond that I really don't know enough about your configuration or apt troubleshooting to help further. I can't try to reproduce your environment, but if you provide the exact error messages from apt, I can search for them.

    However, for faster help, please just simply search the error messages you are receiving from apt that you are receiving and follow the advice of articles that come up on Google. or ask ChatGPT.

    Since I know very little about apt, all I can really do here is read the error messages, search for them, and link you to an article to try.

    Thanks,
    Alana

    posted in Support
  • RE: Ubuntu 24.04.1 InRelease Problem

    Hi @udi-moshe_0021 ,

    Sure, anything would help; I'm basically looking for a very specific error message that I can search. Once you share the specific console outputs, I will try to search what the error means and summarize the results and how you might be able to troubleshoot it further.

    I don't think there are any issues with your ProGet configuration, as it clearly works in Ubuntu desktop for you. It's likely a configuration of apt that you need to make, so you may wish to search the exact apt error messages as well.

    Thanks,
    Alana

    posted in Support
  • RE: Ubuntu 24.04.1 InRelease Problem

    Hi @udi-moshe_0021 ,

    Can you can provide the specific commands and error messages you are receiving? I.e. just coyp/paste the entire console session with the commands you're typing and the output.

    cheers
    Alana

    posted in Support
  • RE: Docker Client for Buildmaster

    Thanks for clarifying that @rpangrazio_2287 , we'll explore that route as well.

    We opted against DinD because of resource management (build servers can be rather resource-intensive) and general instability (not everything seems to work the same).

    FYI - in case you haven't seen it already, BuildMaster does support Image-based Services (Containerized Builds)

    Cheers,
    Alana

    posted in Support