You can use an API key: https://github.com/inedo/upack#push Basically just use "api" as username, and the key as the password.

In this case, you can use the execute command line operation; please see Executing a Command Line Utility During Deployment in BuildMaster

When iam using USB to unlock build master showing error server is not started How can I solve this problem

Maven indexes are for search only, and don't have any sort of sensible ordering, so you won't see packages like you would on npm feeds.

Please refer to KB#1161 for how to update to TLS 1.2

I don't know if there's a better endpoint for this, but I have NuGet feeds and I use a PowerShell script like this: $response = Invoke-WebRequest -Method GET -Uri https://{proget-host}/nuget/Default -UseDefaultCredentials $response.Headers["X-ProGet-Version"]

I have emailed you the white paper that has a hands-on example for this.

Jonathan's correct, there won't be an issue; you can just replace the license key as needed. Of course if you're using paid features like LDAP or retention policy, those will no longer function.

ProGet is primarily developed in .NET (C#) and SQL Server. The front end, of course, uses JavaScript (TypeScript). Our other products use the same technologies

Hi Upgrade Path : Serveur Run the Hub installer on your Otter server -> https://s3.amazonaws.com/cdn.inedo.com/downloads/desktophub/OtterInstaller.exe Extensions (In Admin Menu) /!\ Git Extension shows 1.0.3 after its upgrade while it is expected 1.0.4. but it is working fine Agents. Do not update agent using Otter (Upgrade Agent). I had some trouble with this option. I'd rather upgrade using my software deploiement tools - (Remove old agent, cleanup folder, install new agent) Best Regards Philippe

Apparently this was updated in BuildMaster but not Otter, here is the documentation for the updated version that also applies to yours, substituting $CredentialProperty for $GetCredentialProperty: # ProGetCreds is an instance of Inedo Product Credentials (i.e. InedoProduct::ProGetCreds) with 'Allow encrypted properties...' checked set $key = $CredentialProperty(ProGetCreds, ApiKey); set $host = $CredentialProperty(ProGetCreds, Host); Log-Debug Getting ProGet package from $host with API key: $key; ProGet::Get-Package( Credentials: ProGetCreds, Feed: hdars-1k, Name: hdars, Directory: $WorkingDirectory ); Additionally, I will notify our product director to add an issue to fix this in Otter (it would still be backwards compatible, but the canonical name would become $CredentialProperty)

A 2nd server license is required for this: https://inedo.com/support/documentation/various/licensing/management

I've deleted FTP extension and restarted both BM services. After restart it works properly. Thank you.

ProGet v5.1.16 was just released with the fix included

Are you pushing the same version number? If so, this is (unfortunately) a by-design feature of NuGet. The solution is to use pre-release versioning, or instruct the NuGet task of the build server to always request with the -NoCache flag.

Thanks for the suggestion. We've filed this as PG-1412 for inclusion in a future maintenance release.

Please see: https://inedo.com/support/documentation/various/ldap/troubleshooting#privileges-not-working In short, in Microsoft's AD implementation, Domain Users is not returned as part of the memberOf LDAP property.

Hi Jim, Apologies for the lack of response here, but I wanted to let you know that we had quite a bit of back-and-forth internally on this post and implemented nearly all of your expectations: you are absolutely correct about the variable context not behaving as expected, and the biggest problem was that the behavior of certain variables (particularly $RoleName) was undefined we've updated the docs to reflect the "new" behavior in the latest version (v2.1.0 at the time of this post): https://inedo.com/support/documentation/otter/core-concepts/jobs#orchestration-job-context we release v2.1.0 last night with these changes included Thank you again for the detailed report and reproduction steps.