Hi, Great thanks. Just what I needed. I couldn't work out how to get the list to work. David

It is sent with UTF-8 encoding, and this is sent as an HTTP header as well.

Hi, OK, thanks. Just to let you know, this was from version 5.10 to 5.11. David

This is definitely something we intend to address as part of our v5 roadmap; there just hasn't been a huge customer demand for automating BuildMaster using the sort of "temporary API access key" approach that has grown popular in the more consumer-facing things like Twitter, GitHub, etc. We may add this if there' demand and similar adoption in other tools in the space, but in our experience, it's generally more complicated for administers to manage and set-up. So they just set up one "access key" and give it to everyone. It's particular challenging for us to solve in the same manner because of the way BuildMaster scopes privileges (by application and environment), and because the Native API can work cross-application/environment. So, if it's a requirement to give limited access to Developers, the current best approach is to wrap the native api with a permissions wrapper, and then check if that user is authorized based on the AD group they're in, etc., based on the action they want to perform.

Most definitely! This is what the <b>Asynchronous option</b> on a General Block is designed for. In OtterScript, it just looks like... with async { ... operations to deploy code ... } with async { ... operations to deploy database ... } await;

Ah ha, ok got it! I've identified the bug, and we will fix this in [BM-2003], shipping ASAP!

Thanks; I've logged this as a bug (BM-1999), and we will fix it in the next maintenance release.

Hello; you can request a key from my.inedo.com, and then enter that in the installer. Once installed, there will be activation instructions (because the software can't auto-activate). No internet access is required to install or use BuildMaster.

Well be releasing BuildMaster 5.1 in just a bit (later today), which will have these operations.

Unfortunately we're not able to diagnose this with the information you provided. That error really doesn't make sense in the place it's happening. Can you please submit a ticket with: Configuration Variables defined at various levels (System, etc) Plan as OtterScript Pipeline as JSON Full Execution log, including the full stack trace you sent

BM-1997 - FIX: Transfer-Files operation can create files with \ characters on Linux Thanks very much. Works as expected :-)

Hi Chris, If you haven't already, make sure to check out KB#1118: Legacy Plans in BuildMaster 5.0 to see how to import plans and how the concepts differ. The technique for handling this scenario would be.. foreach deployable in @DeployablesInRelease { «operation1» «operation2» «operationN» } That being said, the @DeployablesInRelease function is not available in v5.0.4, and this specific translation is not handled by the importer, which is a bug in v5.0.4. We will fix this in 5.0.5 and will ship this quite soon (by end of week).

In v4.8, you can set up a Retention Policy or go to Admin > Administrative Edits and purge an artifact. In v5, you will be able to do the same, but purge the artifact directly from the Release Package ("build") page. // I've updated the old question you linked as well

That certainly does sound like a bug. We'll make sure to look into that. The syntax for calling a template in text mode is: call MyTemplate ( arg1: value, arg2: value ); So it's basically just like an Operation except for the keyword "call" in front. That is supposed to be documented here, but it looks like we don't have that listed yet. We'll also make sure to get that added to the docs before we're out of beta. Thanks!

In BuildMaster v5, a global plan is intenteded for use in a pipeline stage/target. Use a global template (Plans > Templates), which can then be called as if it were an operation.

Those 2 steps are working now. I can work on adding back the other steps in the plan/pipeline. Thanks for your help.

Just a quick update -- we also fixed this in BuildMaster 5.0.4.

Thank you. That was the solution. I had already rebooted once, because the Windows Powershell update required it. I rebooted the machine again and now BuildMaster is reporting the correct version. Thanks again.

The BuildMaster NuGet Extension is a wrapper around the nuget.exe client. So it really depends on the client version you're using and how you've configured it. See InstallPackagesOperation.cs