Hi Dean Install and test :). It is working fine. Thank you for the resolution.

That's awesome, thanks!

Hello Damian, I believe this is due to ILIB-60, which is caused by a bug in Mono.

Thank you for the report, this is resolved via: PG-1447

This has also been reported in our Jenkins extensions issues section, can you take a moment to respond to the questions I posed here? https://github.com/Inedo/inedox-jenkins/issues/26#issuecomment-454188149

Hi, i am upgrade my old installlation 5.0.10 to Proget 5.1.20.7 today. And i run into the same issue. My Port customization has been overwritten in the C:\ProgramData\Inedo\SharedConfig\ProGet.config. I fixed it manually and now it works.

Apologies - I broke that endpoint earlier ironically by accidentally disabling logging :( It should work now; I also note that you can request a key at https://my.inedo.com and manually enter it.

Hello Ben Thank you

Hello Ryan, Sorry about the delayed response. The Push to ProGet Visual Studio extension is for Universal (upack) feeds, not NuGet (nupkg) feeds.

Unfortunately this was a regression present in 5.1.19, but has since been fixed in 5.1.20 which was released earlier today.

Here is a working PowerShell example (v6.1+): Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/builds/deploy?applicationName=ApiTest&releaseNumber=1.2.3&buildNumber=1&key=<api-key>" For pre-v6.1 versions, the equivalent is: Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/packages/deploy?applicationName=ApiTest&releaseNumber=1.2.3&packageNumber=1&key=<api-key>" I have also put in a doc change request to clarify the endpoint names. Additional note: -UseDefaultCredentials would be required if Integrated Authentication were enabled.

The latest agent can be downloaded from: https://inedo.com/support/documentation/inedoagent/versions

That worked great. Thanks!

Started new question. Please answer there. Thank you

This should be fixed in v2.2.4, but the issue did not get added to GitHub - I'll correct that.

Hello Simon, I wasn't able to find any information on any standardized way to designate a license in a Dockerfile. I believe the license field in the Docker image pages in ProGet is not filled in by anything.

If it still doesn't work after you've granted anonymous to the feed, then one possibility is that you have WebDAV (caused from a Windows Update?), or a proxy server blocking the PUT request. I've seen that quite a bit..

Hello Ta, I was unable to find any mention of what metadata keys the Docker Hub looks for for those values, but I've filed PG-1443 to display all labels without any special formatting.

Just as an FYI, we're continuing our investigation and exploration of this under ticket EDO-5623 UPDATE: we've addressed a lot of these in the current version of Otter.