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

Is something else listening on port 8081 on the host? ProGet's docker image only tries to listen using a System.Net.HttpListener with the prefix "http://*:80/", which ends up listening on port 80 on all available interfaces in the container.

I tried with secp256k1_openssl_vc120 and the JSON API works as expected. Is there a specific package name that exhibits this problem that you can share?

Ok, I've found the problem: Docker image manifests have a really complicated way to compute their digest:

1. Parse the manifest as JSON, keeping key order.
2. Remove the "signatures" key of the root object.
3. Re-encode the new root object as JSON, with 3(!) space indents, LF newlines, and no newline at the end.
4. 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)

This seems to be caused by there being no feeds defined. In previous versions of ProGet, setup created a NuGet feed by default, but this is no longer the case. Adding a feed will make the Add Package button on the Packages tab work as expected.

Ah, that's my fault. I had assumed that marking it as compatible with Community would also mark it as compatible with anything with a superset of Community's features.

I've marked it as supporting Visual Studio Professional and Visual Studio Enterprise. The update should come out later today or tomorrow.

I am able to reproduce this locally. It looks like you are correct about the root cause being artifactId-version not being a prefix of the filename.

This is a bug. I have fixed the behavior in inedox-git, along with a few edge cases where it would ignore certain parameters.

What you're describing is called a pipeline gate in BuildMaster. For this specifically, I created PipelineStagePromotionRequirement, which can be compiled using the BuildMaster SDK.

The environment on a raft affects who can access it, but not which raft is accessed. Asset names with no RaftName::part always use the Default raft.

There's a bug in the implementation of OtterScript in the current version of Otter that makes it unable to call templates from a non-Default raft.

Running a plan from a non-Default raft is also slightly broken in that it brings up the wrong preselected plan, but selecting the correct plan afterwards works.

You can make an AfterPushPackageAdapter in a plugin. There's an example of an adapter on GitHub.

It looks like running a pipeline on a server role does not correctly set the $RoleName variable.

I've filed this as BM-2381 and it is fixed for the next version of BuildMaster.

I have filed this as PG-757 and it is fixed for the next version.

I can't reproduce the problem you're having. Here's a log of what I tried with ProGet 4.7.4, Docker Machine 0.9.0, and Docker 1.13.1:

PS C:\> docker-machine create --driver virtualbox --engine-insecure-registry 192.168.1.100:83 swarm-manager
Running pre-create checks...
Creating machine...
(swarm-manager) Copying C:\Users\Owner\.docker\machine\cache\boot2docker.iso to C:\Users\Owner\.docker\machine\machines\swarm-manager\boot2docker.iso...
(swarm-manager) Creating VirtualBox VM...
(swarm-manager) Creating SSH key...
(swarm-manager) Starting the VM...
(swarm-manager) Check network to re-create if needed...
(swarm-manager) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(swarm-manager) Found a new host-only adapter: "VirtualBox Host-Only Ethernet Adapter #2"
(swarm-manager) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(swarm-manager) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
(swarm-manager) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: C:\ProgramData\choco
latey\lib\docker-machine\bin\docker-machine.exe env swarm-manager
PS C:\> docker-machine create --driver virtualbox --engine-insecure-registry 192.168.1.100:83 swarm-worker
Running pre-create checks...
Creating machine...
(swarm-worker) Copying C:\Users\Owner\.docker\machine\cache\boot2docker.iso to C:\Users\Owner\.docker\machine\machines\swarm-worker\boot2docker.iso...
(swarm-worker) Creating VirtualBox VM...
(swarm-worker) Creating SSH key...
(swarm-worker) Starting the VM...
(swarm-worker) Check network to re-create if needed...
(swarm-worker) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: C:\ProgramData\chocolatey\lib\docker-machine\bin\docker-machine.exe env swarm-worker
PS C:\> docker-machine env swarm-manager | iex
PS C:\> docker swarm init --advertise-addr 192.168.99.100
time="2017-03-03T11:28:40-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Swarm initialized: current node (kb681q841gbm18jno2ktf157u) is now a manager.
.
To add a worker to this swarm, run the following command:
.
    docker swarm join \
    --token SWMTKN-1-2q02a4egqsnybt7mjb7108zipjwvony48c8iad2kk6dobzt4k8-6ozavuh9gr7vpk1brracn5h6o \
    192.168.99.100:2377
.
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
.
PS C:\> docker-machine env swarm-worker | iex
PS C:\> docker swarm join --token SWMTKN-1-2q02a4egqsnybt7mjb7108zipjwvony48c8iad2kk6dobzt4k8-6ozavuh9gr7vpk1brracn5h6o 192.168.99.100:2377
time="2017-03-03T11:29:38-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
This node joined a swarm as a worker.
PS C:\> docker-machine env swarm-manager | iex
PS C:\> docker pull nginx
time="2017-03-03T11:31:42-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Using default tag: latest
latest: Pulling from library/nginx
693502eb7dfb: Pull complete
6decb850d2bc: Pull complete
c3e19f087ed6: Pull complete
Digest: sha256:52a189e49c0c797cfc5cbfe578c68c225d160fb13a42954144b29af3fe4fe335
Status: Downloaded newer image for nginx:latest
PS C:\> docker tag nginx 192.168.1.100:83/dockertest/nginx
time="2017-03-03T11:33:11-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
PS C:\> docker login 192.168.1.100:83
time="2017-03-03T11:33:20-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Username: Admin
Password:
Login Succeeded
PS C:\> docker push 192.168.1.100:83/dockertest/nginx
time="2017-03-03T11:33:40-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
The push refers to a repository [192.168.1.100:83/dockertest/nginx]
e3a86ffb1c45: Pushed
cf0d2468e726: Pushed
d17d48b2382a: Pushed
latest: digest: sha256:32e3cf2703f4e8f99426884247f9e0d4d5acdde4914fe7df70f74c76ba6216fe size: 6300
PS C:\> docker service create --name q-6011 --replicas 1 --constraint 'node.hostname==swarm-worker' --with-registry-auth 192.168.1.100:83/dockertest/nginx:latest
time="2017-03-03T11:35:29-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
unable to pin image 192.168.1.100:83/dockertest/nginx:latest to digest: missing or empty Content-Length header
5x9ctqpt9d2duv8gblzpws4ed
PS C:\> docker service ps q-6011
time="2017-03-03T11:36:19-06:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
ID            NAME      IMAGE                                     NODE          DESIRED STATE  CURRENT STATE           ERROR  PORTS
lcsz1x2ndgda  q-6011.1  192.168.1.100:83/dockertest/nginx:latest  swarm-worker  Running        Running 58 seconds ago

The patch I submitted makes PSCall able to use output variables that are % and @ in addition to the $ variables it already supports.

It looks like that @PSEval call is returning the string "System.Collections.Hashtable".

I did some research and the reason is that PSEval returns the output of the script as a string.

Using this PowerShell script:

$var1 = 'serviceName'
$var2 = 'type'
$serviceList = @{}
for ($i=1;$i -le 5; $i++) {
    $serviceList.Add($var1+$i,$var2+$i)
}

And this OtterScript:

pscall PsScript
(
    serviceList => %serviceList
);
foreach $key in @MapKeys(%serviceList)
{
    set $value = $MapItem(%serviceList, $key);
    Log-Information Key: $key;
    Log-Information Value: $value;
}

I've submitted a patch that will make it do what you want.