This means that your computer cannot connect to My.Inedo for alicense key. Please request one by logging into my.inedo.com.

A vulnerability version range can be: the literal string (any) empty string (equivalent to (any)) single single, single single, single, single single, single, single, single etc. A single vulnerability version range can be: version >version >=version <version <=version >version <version >=version <version >version <=version >=version <=version The format of version is defined by the feed type.

Version 1.1.0 of the upack command line tool is now available from http://inedo.com/support/documentation/proget/reference/upack. The chocolatey version has been submitted and will be available once it's approved.

There's a bug we haven't been able to figure out where the Linux version of ProGet doesn't respond to requests for URLs with colons in them.

I see you also opened a ticket, so it's going to be best to collaborate on that instead. But I will respond here as well in case anyone finds this... Unless you're entirely distributing third-party, vendor-provided packages (i.e. you don't move them through a pipeline like Dev > Test > Prod), then BuildMaster is quite important to manage this pipeline , especially in regulated environments. Regarding HA, it's best to first come up with a list of questions you'd like us to help with, and then we can research and figure out how best to help. For example, we can't really help on selecting or configuring a particular brand of load balancer; that's something generally done by your IT/NetOps folks, but we could point you to Microsoft's NLB documentation (which has step-by-step instructions on how to set it up).

Configuration file versions and database change scripts must be tied to a specific release number, so we create 0.0.0 to associate those. It might be best just to purge that release if you don't really use it.

Perfect. Now it works as expected :-)

That is good news, i was able to bypass this though by setting the service to run as an outgoing trust user which then allowed me set the LDAP to the other domain.

This appears to be an internal Java error, indicating that the package cannot be bufered due to low process memory. So, I would increase the memory of your Java/Jenkin instance. You can use the -Xmx1024m option to give 1GB of memory to your application. This will increase the amount of data you can store in memory.

That fixed it, argh! Been messing with this for hours! Thanks!

It's cool, I switched to global template to be called. It works fine. Thanks!

I agree that it is a poor solution, but we do not have very many good solutions for this. Docker itself does not support prefixing private repositories; everything is assumed to be hosted in the same manner as the public registry (ie, absolute URL path from the server root), and assuming all /v2/ requests are Docker without some other declaration of intent in the request didn't seem good either. That said, if there's no collisions with anything else using that URL, we can change the default behavior.

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.