ProGet 4.0.11 is now available, which includes support for scoped packages. You can get it from the downloads page: http://inedo.com/proget/download

Thanks, all good now.

Unfortunately, when symbol serving doesn't work, it can be a pain to diagnose... Can you "start from scratch", documenting your steps along the way, so that I can try to reproduce exactly what you're doing? Start by making a very simple, hello world sort of library (maybe one class, with some basic code you can easily step/through and debug). After that, then create some brand new feed (it sounds like you want two feeds? a symbols and a package feed?), then configure the new feed in Visual Studio. Then follow the other steps, like seeing if you can find the symbols in Visual Studios, etc. If you can share the exact steps you did, and the package you upload, then I can reproduce the error you're seeing by following steps using the package.

Alex-Hempel said in Proget Jenkins Plugin: Not working on Slaves?: Caused by: java.io.NotSerializableException: com.inedo.proget.jenkins.DownloadPackageBuilder java.io.NotSerializableException can occur when you serialize an inner class instance because serializing such an inner class instance will result in serialization of its associated outer class instance as well. How to solve it? If the class is yours, make the class serializable by implementing the interface java.io.Serializable. All non primitive members implement Serializable (or are transient instead) If your class is an inner class it's either static or the outer class implements Serializable If the class is 3rd party, but you don't need it in the serialized form, mark the field as transient It is important to note that Serialization of inner classes (i.e., nested classes that are not static member classes), including local and anonymous classes, is strongly discouraged.

Hi Alana, This seems to work for what I am trying to accomplish. Thanks! Scott

Hi @dm-sidelnikov_5266, Glad to hear it! Please let us know if you have any other questions. Thanks, Rich

Thanks for the quick fix. We didn't have that many packages assigned to the licenses in question, so the workaround of disconnecting all packages from a license and then deleting that license did the trick.

Hi @j-d-koning_0111, Just wanted to check in if PG-2738 fixed your issue. We have also been working with another customer that has had similar issues. We determined this was related to setting to Map groups to SAML groups setting. If you have this enabled and do not have any groups claims sent, it was causing the error you saw above. This last issue, PG-2745, will be released in the next maintenance release. As a work around, make sure you have your SAML provider configured to send groups claims. Thanks, Rich

Did the multi-part API get implemented for universal packages? This is still an issue.

Great to hear! Thanks for the followup

I am one of the developers, which is why I can assure to you that ProGet is not issuing a 503. This is IIS. However, based on the new information you've provided, it's likely happening because of an abrupt Application Pool termination such as a access violation, stackoverflow, etc. In such a situation, it's not possible for ProGet to log anything; the program (AppPool) immediately crashes. Then IIS issues the 503 error. However, IIS should be logging these in the Windows Event log; so if you can look into what it is, then we can try to debug it further. This is an easy scenario for us to set-up, and it's a common error condition, but we cannot reproduce it.

Surfing Pikachu, That was one of the steps I mentioned in my original post. Did not work for this issue. Alana, Already attached Fiddler before original post. Just showed 404's for symbol requests. Downloading the package locally allows the symbols to be found; but using ProGet's symbol server doesn't work.

I found the issue. User error on my part. This is a small plan that handles this and I had a Legacy plan doing something similar but not using the Promote API. The pipeline was still pointing to that old plan and I just didn't notice the calls going to Proget. Then I was working on the new plan so as far as I knew it wasn't using the filename but in the old plan it was. Changed to the correct plan and the Promotion worked fine. Sorry for wasting your time on this.

Thanks. That of course fixed it.

That's great news ! Thank you for following up :)

Thanks, Tod. That works. I appreciate it!

Fix verified on 2024.2 version. Thank you.

That worked! Definitely a big work around. We additionally had to set the AppPool for the new site to Classic and disable Forms Auth in the bindings.

Hi @w-repinski_1472, We currently do not have any mechanism for alerting the user when an extension update is available. Our guidance around this is to check extensions for updates after a product is upgraded or when instructed by support. In this case, it was my fault for not alerting you to upgrade the extension to fix this issue. I'm sorry for that and I will make sure this does not happen again. Also, many extensions are included in the install package. These extensions are updated automatically when the product is upgraded. So this won't be a problem with most extensions, it just so happens that the clair extension is not an included one. Please let me know if you have any other questions for us. Thanks, Rich

Many thanks for that proposal, Steve! The warning label in conjunction with dumping of the package cache sounds like it is worth exploring. I shall discuss it with my security and governance collaborators :-)