Hi @forbzie22_0253 , That's not exposed in the UI at this time; is there a reason/use case you'd want to use it? it's primarily intended as a kind of backup of sorts. Thanks, Alana

Had to set ownership on the folder on the Linux server, all green now thanks!

Hi @daniel-lundqvist_1790 , You can select the edition you'd like to trial within the software itself, under Admin > License Key. Thanks, Alana

Hi @zs-dahe , The Package Promotion API only be checks for permission against toFeed - you don't need any other permission on the toFeed or fromFeed. As far as more granular permissions, perhaps setting up a Personal Key for like a builds user would do the trick? That'll let you reuse the API Key and set up very granular permissions. We decided not to duplicate that granular permission setting in the API Keys because it's already confusing enough Thanks, Alex

@davidroberts63 thanks for figuring that one out, that's definitely bug... ... box style was correct, but enabled/disabled text looked at wrong property Easy fix, difficult to spot!

Hi @marc-ledent_9164 , Are you referring to the Machine UID from Manual Activation? I'm not sure what the Machine UID looks like in BuildMaster 7 on Linux, but I do recall that early versions of our products sometimes couldn't generate the string on some hardware. I think that's fixed now. The code is supposed to be based on the CPU (vendor ID, model, family, and stepping info) and the and the major version of the Inedo software (e.g. 5.1, 5.3, 2022, 2023). Thanks, Alana

Hi @gdivis, I've tried encoding the purl URL, and it works on both Windows and Linux, without having to interchange the distro and component order. However, it's a little strange that NuGet package purls work whether they are encoded or not. Anyway, I'm going to encode the URL in the code. Thank you very much.

Hi @caterina, We're a bit concerned that this is too specific for your usecase, and we're really struggling documenting it. Instead of doing this, we're thinking it might just make more sense to run (Get-Item 'C:\path\to\file.exe').VersionInfo using PowerShell and export these into variables instead. For Example: $versionInfo = (Get-Item 'C:\path\to\file.exe').VersionInfo $version = if($versionInfo.FileVersion) { $versionInfo.FileVersion} else { $versionInfo.ProductVersion } $productName = $versionInfo.ProductName pgutil builds scan --input=myApplication.csproj --project-name$productName" --version=$version Thanks, Dan

Hi @atripp, thank you for the clarification. I can confirm this behavior. Thank you very much, Caterina

Hi @atripp , thank you for the info and clarification.

Hi @atripp, We haven't updated the production instance to the version that introduced this feature yet, so nobody breathing down my neck. ;) I'll wait for the official release, but thanks for the offer. Have a nice weekend!

I've seen your message yesterday. I will investigate as soon I have the correct environment. Thanks for the help!

Hello Alana, Yes, you are right. AHVALUEDRIFTED has to be a boolean value. The name implies it actually but I did not connect the dots. Thank you for the help!

Hey Alana, sorry for the late response! And thank you for the update. You are totally right, this will not happen often, even rare, so I think we can work with this solution. :) Have a great day, Frank

Hi @forbzie22_0253 , Yes, we use Kestrel under the hood. You can configure HTTPS under Admin > HTTPS: https://docs.inedo.com/docs/installation/installing-on-iis/installation-windows-https-support No real "gotchas" -- but note that with port sharing (i.e. binding to a hostname as opposed to an IP), that needs to use the HTTP.SYS component of Windows. Cheers, Alana

Hi @gdivis thank you for your response. This is what I was looking for! Thanks, Caterina

Hi @marc-ledent_9164 , That refers to our build server :) That part of the error message is the stack trace, and that shows us exactly where the error is occurring in the code, should we need to debug it. That said, if you're seeing those errors in your execution logs, then it's probably related to configuration of some kind..... we can help if we could see more context Cheers, Alana

@tekla-buildmaster_8300 it's on our list for this year :) https://blog.inedo.com/inedo/roadmap2025/

Thank you, @atripp. Appreciate your suggestions.