I'm not familiar with Zabbix, but there are two things you can do to check about the status of the components (Database, Web, Service): If the database (SQL Server) wasn't working, or there was a problem with the website configuration, then visiting / will yield a 500 or some other not available message. You can just query the ProGet service run state directly. You could parse the text on the /connectors page or use the native API to get a status of the connectors.

Hello Pedro, Docker feeds appear to have been missed when the api user was added for feed authentication. I've filed PG-1295 to fix that. ProGet 5.1.0 is not released on Docker Hub, but you can build the image locally with this command: docker build -t inedo/proget:5.1.0 --build-arg PROGET_VERSION=5.1.0 github.com/Inedo/proget-docker

Use permissions for this. There is a Feeds_OverwritePackage task or something that you can remove, or restrict as you see fit.

Hello Paul Here is the powershell script we are using. It is running from the server as a part of our init server script. We deploy the Otter/BuildMaster Agent and we run the script . Hope this help Regards Philippe Param( [Parameter(Mandatory=$false)] [string]$API = "https://#OTTERHOST#/api", [Parameter(Mandatory=$false)] [string]$SERVEUR = $env:computerName ) #end param # Extract AESKey [xml]$XmlDocument = Get-Content -Path "C:\Program Files\InedoAgent\InedoAgentService.exe.config" $AESKey=($XmlDocument.configuration.appsettings.add | where-object {$_.key -eq "EncryptionKey"}).value # # Grab list of registered server # $URI=$API+"/infrastructure/servers/list" $aListServer=Invoke-RestMethod -Method Post -Uri $URI -Headers @{'X-ApiKey' = '********************'} if ($aListServer.Name -contains $SERVEUR){ # # Mise à jour # $URI=$API+"/infrastructure/servers/update/"+$SERVEUR $body = @{ name="$SERVEUR"; hostname="$SERVEUR"; active=$true; serverType="windows"; port="46336"; encryptionType="AES"; encryptionKey=$AESKey } }else{ # # Creation # $URI=$API+"/infrastructure/servers/create/"+$SERVEUR $body = @{ name="$SERVEUR"; hostname="$SERVEUR"; serverType="windows"; active=$true; drift="automaticallyRemediate"; port="46336"; roles=@("Baseline"); environments=@("Integration"); encryptionType="AES"; encryptionKey=$AESKey } } # # Appel de l'API # Invoke-RestMethod -Method Post -ContentType 'application/json;' -Uri $URI -Body (ConvertTo-Json $body) -Headers @{'X-ApiKey' = '********************'} #

It shouldn't, and if you're using SSL then it's encrypted traffic and nothing can "capture" it between... but keep in mind that ProGet is really only providing the server-side API. If you write a script (or use a tool) that logs all API calls to ProGet, or logs the full call to nuget.exe, then whatever you log is going to be logged.

There isn't currently, but there will be soon! Please see PG-1221 I can't imagine any reason at all this wouldn't be done, and it can go it the next maintenance release assuming it passes code review etc! Thanks much for the specific suggestion!

Hello Emil, If source or symbol stripping is enabled on the NuGet feed, the package you download will be dynamically created. If you add a query parameter ?includeSymbols=Y in the package request, ProGet will give you the original nupkg file, which should have the SHA512 sum from that field.

It doesn't, but I think we should add it to the Release & Package Deployment .. so I added BM-3149 So, it will come in a future maintenance release, since it's additive and seems to pose minor risk.

Outstanding, thanks Alex

Package promotion is a paid feature; please see Features by Edition.

It's just an unfortunate mix of terminology in "promotion" vs "deployment" vs "execution". A "promotion" is simply allowing a package to be deployed to the stage and should only happen once per release. A "deployment" can happen anywhere but may be restricted by pipeline settings depending on if the package was previously promoted, and an "execution" is essentially the worker that performs the deployment (and there could be many per deployment). The fix will make it perform a deployment instead of a promotion then a deployment, so it will work as you're expecting.

Can you provide the full stack trace? It will be logged in Admin > Errors.

I'm guessing that you're referring to this from the docs. I'll give it a try. ...Feed API key authentication is performed using HTTP basic authentication. To authenticate using a Feed API key, supply "api" for the user name and the API key for the password. feed api keys

The release/deploy API is secured by API keys, not by username/password. When you configure an API key, you can determine which access that API key has. Treat those API keys like passwords, and share them only with people you trust.

Hello Megha, In PowerShell, to create a JSON object key with a dollar sign in it, you need to use this syntax: "`$KeyName" So your object would look like this: $CreatePackageParam= @{releaseNumber=$ReleaseNumber; applicationName=$ApplicationName; "`$SiteName"=$SiteName; } Otherwise, PowerShell replaces both instances of $SiteName with the value in that variable.

You are using it correctly; there is a bug in that particular endpoint that ignores the variables for non-legacy plans, see: Issue BM-3077

As far as we can tell, ProGet has never returned a 409 response from that endpoint. A quick Google search reveals this NuGet bug: https://github.com/NuGet/Home/issues/2910 You can fix this by upgrading to NuGet.exe 3.4.5, NuGet.exe 3.5.0-beta2, or a later version.

Thanks, Tod. That works. I appreciate it!

Hi Megha, Per the Release & Package Deployment API, you must POST or PUT to this url. On the Invoke-RestMethod CmdLet, you specify this using the -Method argument. $response = Invoke-RestMethod 'http://<<BuildMasterServer>>/api/releases/packages/create?releaseNumber=1.0.2&applicationName=DeployWWMapping&key=5WRTeJcctiY32u2bEqTb4Q==' -Method Post

Hello Megha, That URL looks correct. Are you doing a POST or PUT request, or a GET request? If you're visiting the page in your browser, that's a GET request and it won't work. Either POST or PUT will work, though. You can use a web hook to automate this through TFS.