Hi @parthu-reddy, For a major upgrade, we recommend to schedule a maintenance window and then stop traffic from the load balancer. Then, upgrade the servers. For a maintenance release, it's fine to just upgrade them one at a time. It only take as few minutes to do that. There may be a few errors with the database/code being out of sync, but it likely will not cause any problems. -- Dean

@dean-houston Thanks

Hiya, We changed the setup to root, but still encountered the same issue. Besides rootless container policy we're also doing segmentation of every platform, so only allowing powershellgallery.com wasn't enough. after extented search and looking through logs we saw that the CDN's of powershellgallery were being dropped. Will probably revert the setup and go back rootless after the holidays to see if everything still works flawless, be I guess it will be fine now :) Thanks for your insight!

@sneh-patel_0294 I don't think so, its only displayed on that page...

@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

I am also against DinD because the way I saw it done involved installing a specialized runtime and I'm not particularly crazy about doing that. I'd like to find a more portable way of doing it. I admit I am new to Proget/BuildMaster/Otter and really like it so far. So I am sure that I will engineer some solutions that are, to be frank, Rube Goldburg-esque.

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

@atripp hi, i already searched the internet and found nothing helpful. this is why i turned to you . as said, i will start over and try to give you the output. thanks, udi

Hi @atripp , Thanks for the suggestions. Concerning the LogMessages table, we already have those messages displayed on the OpenShift console, but nothing suspect can be seen. What I'll try is to test a fresh install of the last BuildMaster version and see what difference we have with our "updated" version. I'll keep you in touch. Marc

Hi @paul-kendik_9721 , It looks like you're on the right track with troubleshooting -- the issue is indeed related to SSL/Certificates. This is all handled at the operating system level, which means there's nothing we can do on the application (i.e. ProGet) side of things. Unfortunately, I've never seen this error on a modern Windows server so I don't know what exactly to suggest to fix. I didn't even know TLS 1.0 was enabled on Windows still. Maybe it's not even the server, but like a proxy or some kind of intermediate server? The "good news" is that this is an easily searchable problem, so I would start by searching for "Windows 2022 SSL HandshakeFailure TLS 1.0" and see what comes up. There is certainly some kind of setting on your server taht is causing this problem, I just don't know what to suggest to look for. Please let us know wat you find! Alana

@daniel-lundqvist_1790 no problem.. docker is really confusing/silly... , glad we got it solved :)

@atripp Thanks for your reply... This is a good reason to planify an upgrade! Marc

According to https://docs.inedo.com/docs/proget/feeds/other-types the Composer feed type is planned for a maintenance release of ProGet 2024, which is great news! We're currently using Satis for PHP packages alongside ProGet (for NuGet, npm, Python). Working with Satis is a bit cumbersome, that's why we would very much prefer using ProGet for PHP packages, too. Satis downloads the distribution zips for all packages and generates a static site with package metadata and the zips. I guess ProGet will handle Composer feeds in a similar fashion? Feel free to reach out to me via email if you need further feedback or beta testers for the Composer feed type.

Hi @steviecoaster , Very cool, looking forward to the packages! Here is the URL for the ProGet license agreement: https://inedo.com/proget/license-agreement The Inedo Hub does not have a separate license agreement, we just consider it part of the product; so you can just use ProGet's: https://inedo.com/proget/license-agreement Thanks, Nanci

Hi @Dony-Thomas_7156 , You can ignore these errors. ProGet doesn't process these requests (i.e. store the content); instead ProGet simply generates the appropriate hash of a maven artifact when you request .ext.md5, etc. It's dynamic, not a file system. That said, I do know that later versions of ProGet will simply return a 200 so that it does'nt cause an error with Marvin. I recommend to upload to the latest ProGet 2024, and use the New Maven feeds. Thanks, Alana

@atripp Thanks for the response. Seems we are using a quite old version of Proget - Version 2022.25 (Build 9). We are planning to upgrade it in a few months, but didn't think it would cause issues. We might have to wait for an upgrade to our systems to get this fixed then.

Hi @daniel-lundqvist_1790 , Good question! ProGet 2024 ships with the latest version of all available extensions, so there's usually not going to be a new one unless we add ones later (e.g. GCP) or update/fix ones. Most extensions are used by BuildMaster; for example, the Jenkins extension lets you do cool stuff like import/orchestrate Jenkins servers and deploy artifacts from them: https://docs.inedo.com/docs/buildmaster/tools-service-integrations/buildmaster-integrations-jenkins Thanks, Alana

Hi @forbzie22_0253 , We have never seen a case where changing an IIS setting has benefited performance in any way whatsoever; instead we have only found headaches and problems from users modifying them. Those settings are not designed for modern .NET applications, but for like .NET Framework, classic ASP, etc. So please don't touch them :) Thanks, Alana