This has been added as BM-3004, and is currently scheduled for 5.6.10.

This has been on the list for a little while, but I finally made a github issue for it. We'll get it soon! https://github.com/Inedo/inedox-inedocore/issues/22

In this case, you will need to give the "Anonymous" access to push packages to the feed. You can configure this from Admin > Tasks.

Just as a follow-up, we are going to clarify this behavior and "fix" it to be more like your use-case, see: http://inedo.com/support/questions/6290#inline-post-6291

The problem here is that there is not exactly 1 environment in context. I'm guessing this is an orchestration plan? Configuration plans will already bring in the environment context if there is exactly one environment. The way this will be solved (targeted for v1.6, but may appear earlier in a v1.5.X maintenance release) is by the following rules: Context will solely be determined from environment associations of servers (this changes the current behavior which relies on orchestration jobs being targeted at an environment in order to bring the environment into context) Parent environments will only be considered for user permissions and variable resolution If there is not exactly 1 environment applicable to the current server in context, $EnvironmentName will result in an empty string (so the same as you're seeing now) We will add @EnvironmentNames which will resolve to a list of all environment names in context (including an optional parameter for including/ignoring parent environments)

We have responded to this via the ticket you submitted, can you verify that you received it? Today we switched to a new automated ticketing system and I want to verify whether you received an email update or not from the system. Here was the response: In BuildMaster v4, these are configured on the Admin > Extensions > Source Control Providers page for the specific provider in the URL of the remote repository itself, e.g. https://user:pass@example.com/remote.git

The endpoint is not yet deprecated. This error means that connector url is incorrect, npmjs.org is returning an error, or you have some proxy server blocking the request in between ProGet and npmjs.org.

Tried stoping the service that was tying up port 80. No help.

I can't get the Visual Studio 2012 or 2013 SDK to install. In the meantime, you could try building the extension locally with the reference to the 2015 DLL changed to the 2012 or 2013 version: https://github.com/Inedo/VsPushToProGet

The npm endpoint to get all packages is /-/all, so in your case: http://dr-tj-pkgsvr01/npm/npm/-/all

The native API is a database wrapper, and thus would only be able to return local/cached packages. You should consider using the NuGet API instead.

Thank you for the report, we are in the process of releasing a hotfix (v1.5.5). It should be released within the hour.

As of v4, ProGet will no longer support packages pulling packages with dependencies from the UI. This is because it's "impossible" to do without visual studio's context (target framework, .net version, etc).

That operation looks exactly like what I am trying to achieve. What is the behavior when all of the servers in the pool have been acquired? Does current execution wait or does an error get thrown?

Well, for this, you would use the Download package endpoint There's a lot of guides out there on how to use cUrl (here's a good one), but a basic use would be... curl http://proget.local/upack/my-feed/download/my-group/my-package/1.2.3?contentOnly=zip -o my-package1.2.3.zip ... then you can just use unzip.

Ok, I've found the problem: Docker image manifests have a really complicated way to compute their digest: Parse the manifest as JSON, keeping key order. Remove the "signatures" key of the root object. Re-encode the new root object as JSON, with 3(!) space indents, LF newlines, and no newline at the end. Compute a SHA256 hashsum. The problem was that on Windows, ProGet re-encoded the new root object with CRLF newlines. This is fixed for the next version. (4.7.7)

Hmm, sounds like a NuGet/VS bug... definitely worth sharing this with them!

We anticipate the end of this week or early next!

Please request a key at My.Inedo

THis is logged as a bug for [PG-758], and we may get this in next maintence release. Unfortunately it's a non-trivial fix.