Hi Christian, the information you posted had mentioned internal packages (Aeon Framework, etc), so I removed it That said, it wasn't an error message, but a JSON document that contained metadata information about packages. This is an expected response if you visit an API URL directly in your browser, and when the npm client relies on the JSON data. If you are receiving an error from the npm client, please make sure to share: the precise error message that npm client is using the precise URL that the npm client is requesting; you can get this by running Fiddler, and seeing the requests that the client makes Note that you will need to disable Windows Integrated Authentication at the IIS level, not just within ProGet.

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.

This is not possible, because that is not a package (but a git repository).

This was removed when all the feed pages were combined (NuGet was the only feed type with an additional filter). We'll have to figure out a good way to add it back - it should be returned in an upcoming maintenance release of v4.4.

See: http://inedo.com/support/questions/5371

Do you have specific guidance on how to setup the separate site?

We refactored a lot of the user-interface code for ProGet 4.4, so this is unfortunately a regression introduced due to those changes. I've logged the issue and it will be fixed in the next maintenance release.

You can temporarily use your key for this purpose, that's quite alight. Just enter the key in, and it will activate.

Well i finally was able to publish to our Powershell feed. I updated the PackageManagement and PowerShellGet modules to version 1.1.0.0. which were released a few days ago... 12 Oct 2016 I hope this helps .

It's still on our roadmap, but it was pushed back to 4.7.

Looks like reinstall helped. Thank you!

This is a limitation of npm unfortunately; scoped packages are not included in the npmjs.org index, therefore there is no way to search for a scoped package via a connector. However if you already know the name, then it will work, and can be retrieved from the connector.

It's not an option, but your best bet to solve this would be: Bulk / Droppath Import from Disk (any packages) Feed Replication (from another ProGet server)

Thanks for the report, this is a bug in the UI, and it's missing the "/" between the "host name" and "api". We will fix in next maintence release of ProGet.

Thanks, will try IIS rewrite module for that.(

Hi Ruben, this was a regression in v4.4 after redoing the UI for the combined feed pages. We will fix ASAP in the next maintenance release under [PG-626].

That is just a "regular" COM+ that happens every now and then when doing anything with LDAP, so you an usually restart IIS, restart the server to fix it. Will send the code ASAP!

This is not currently supported nor is it currently on our product roadmap.

Well if you used "npm" as a source, and then set up that as a registry in ProGet, then it could be a source.