Thanks Alana, once I installed the certificate into my 'Trusted Root Certification Authorities' and restarted the docker daemon on my client machine, things are working nicely. Thanks again for your help!

Unfortunately the Native API is essentially a database wrapper, and one of the few things that can't be handled at the database layer is encryption. While we want to create a resource credential API at some point, in the meantime, the only workaround would be to encrypt/decrypt the secrets yourself, using the Encryption Key stored in your configuration file.

Hello Alana I agree. I know that one server should be assign to a single Environment. I already use Role for the Applications (One Role = One Application), but I cannot have 1 or more server per environment as our dev team and test team like to have plenty of environment so I need to consolidate multiple environment to one server. I am already using BuildMaster (with many Pipeline Stage) to deploy to a single server the environment I want. It was a request to improve Otter which already good to make my work more simple. I understand it might not be very simple to do it. Thank you for the reply Best regards Philippe

The SQL server and the application are both on server 'Production' and the application is successfully retrieving data from the SQL server. The connection string used in the application configuration is the same connection string being used in the SQL connection in Buildmaster. It is using a SQL account, so not integrated. Here is a redacted connection string: - Data Source=*************;Initial Catalog=*************;User Id=*************;Password=*************;MultipleActiveResultSets=true;

You got it working though :)

After doing the steps in the links, I was able to remove and re-install proget (using offline installer). After that, Hub still didn't work, so I tried running the online-installer which downloads the Hub at the beginning of the install and that seemed to fix the Hub. Thanks for your help Dean.

The groupName refers to the package's group name, and it's optional. A universal package is identified by group + name + version. The files do need to be artifacts; that's what will be zipped up and sent to ProGet.

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.