If you are using IIS, you'll need to make sure that the ProGet AppPool is set to use Integrated Pipeline mode. If hosting with the integrated web server, it should just work. You may also need to enable always-auth for npm to force basic authentication.

Definitely! We're really not thrilled on how the current legacy Actions work (they were built by a third party, and also during a time that Azure underwent so many changes), so we'd like to update them to make more sense and be more useful... We'd love to understand your usecases, and how we can make the BuildMaster/Otter Azure integrations great. It'd be quite a bit easier to do this outside of Q&A though, so let's get in touch via email!

Please upgrade to the latest version of ProGet; 4.3.1 is outdated.

Note that these are different issues. Please upgrade to the latest ProGet to resolve this and the other issue. As of this post, that's 4.7.8. However, we do release often so if another one comes out before then, pick that one :)

Answering my own question: all one needs to so for this is to remove the Anonymous user from the users allowed to "View and download packages".

This can be found in the lower-right of any page in the software.

I found this thread after experiencing a similar issue. I was seeing the "string is not a valid semantic version error" from Proget when npm would try to install scoped packages, but only when the npm install was automatically triggered inside Visual Studio by a change to the package.json. We already had the latest version of Proget with the change to the web.config and installs worked fine when running from command line. Problem turned out to be the fact that Visual Studio 2015 had installed it's own copy of the npm.cmd as an external web tool. This was an older version than the one I had installed globally, but the order of external web tool locations in Visual Studio had the path to the older version listed before my system path. Making system path take precedence solved the issue. [image: 0285.tools-options2_15477577.png] Just thought I'd post this here in case anyone else with a similar issue stumbles across this thread like I did.

You can configure this via the "BaseUrl" setting in the Admin > Advanced Settings configuration option.

There are many guides and ways to do this, please search "adding a maven artifact to a repository". Here is one such example: https://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html

This is on our list for an upcoming maintence release, and may get implemented in the next one. you can check the status of it at PG-1001. https://inedo.myjetbrains.com/youtrack/issue/PG-1001

This package indicates that the package you are adding is in an invalid format. If it's a nuGet feed, you must upload a nuget package. If it's a universal feed, you must upload a universal package format.

Well, the only code path that will yield that error is if System.IO reports that the file requested is not on disk. The most likely cause of that is that the file is not actually there at the time (obviously), but that might be because anti-virus quartanteed it, a file server didn't replicate it, or something? So, I would try to find what might be causing that file not to be there. The only way that BuildMaster will delete a file (but not the record) is a retention policy.

Ok I figured out what I was doing wrong. I was setting the URL in build.gradle to: http://<user>:<password>@proget-server But it should look like this instead publishing { repositories { maven { credentials { username "$mavenUser" password "$mavenPassword" } url "http://proget-server" } } } With the mavenUser and mavenPassword being defined in ~/.gradle/gradle.properties

Correct; that, and the API key, are what get sent over.

Correct. Output variables don't need to be specially declared. However, the next version of the Windows plugin for BuildMaster and Otter will add support for [ref] parameters as output variables in the editor.

I'm on ProGet Version 4.7.8 (Build 4) (locally hosted, not on EC2) and I'm able to upload universal packages to an S3-backed feed using the upack.exe tool with both the latest published release of the Amazon plugin and a debug build from source code. Can you still reproduce the error on the latest version of ProGet?

Thanks. That of course fixed it.

Thanks Tod, I guess I was overly enthusiastic for this feature ;)

MaxResponseLength was missing a ScriptAlias. It'll be fixed in the next release.

Apparently I was an idiot and couldn't do basic auth correctly, because once I did that correctly it worked fine without anonymous access involved. I am using Java 8, and the Authenticator class to set the authentication on my URL globally. Hope this helps the next person coming along.