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.

The Docker Client does not support integrated windows authentication; as a work-around, you'll want to set up a second ProGet site (different port or host name) in IIS that points to the existing folder but doesn't use integrated authentication.

Great to hear it got fixed. Thanks !

You can either use the Release Name for this, or you can use a combination of Build and Release number to create a four part version number ($ReleaseNumber.$BuildNumber)

Please carefully follow the Getting Started with NuGet Feeds in ProGet and Visual Studio tutorial. You need to use the API endpoint URL (shown to you within ProGet's Feed page), not the URL that you at the top of your browser. The /feeds URL is intended for use by a web browser, and the /nuget URL is used for an API (i.e. Visual Studio).

Glad to see it's working; but just as an FYI, the installer does not have any code that can delete the database. That's only in the uninstaller program, and that needs to be manually run with double-confirmation (in the UI).

Just seen that .18 has been release. Tested and working. Ignore above.

Thanks for the report; I've logged this as OT-280

That message is expected, if it's already an updated database. Please check out the restore procedure outlined in Backing Up ProGet instructions

Hello Attila, If you run docker inspect proget -f '{{json .Mounts}}', does it include /var/proget/extensions as both the source and destination of one of the bind mounts?

This is on the all versions page, just click "Traditional Installer".

Thanks Justin; we definitely need to improve docs. I just made a change to it now to clarify this better: https://github.com/Inedo/inedo-docs/blob/master/ProGet/feeds/maven.htm

John, while on the subject of execution ID's and such, during the logging of a psensure, can we add the psensure key to the log so it always outputs what it is checking and validating? How it is now: INFO : 2018-12-11 20:31:07Z - Configuration drift detected. DEBUG: 2018-12-11 20:31:07Z - Adding to execution plan. DEBUG: 2018-12-11 20:31:11Z - Collecting configuration... DEBUG: 2018-12-11 20:31:11Z - Comparing configuration... INFO : 2018-12-11 20:31:11Z - Configuration matches template. DEBUG: 2018-12-11 20:31:14Z - Collecting configuration... DEBUG: 2018-12-11 20:31:14Z - Comparing configuration... INFO : 2018-12-11 20:31:14Z - Configuration matches template. and so on. Maybe it could log something like "Collecting configuration <key>" and "<key> matches template". That way it would make each line meaningful and bring more value into keeping the logs. Eventually I would like to have a way to save a copy of the txt execution into servicenow so we have a record of it in change management system as well. The url you shared previously will help in doing that I think. This improvement would help as documentation for each change. Thanks!