Definitely! We're really not thrilled on how the current legacy Actions work (they were built by a third party, and also during a time that Azure underwent so many changes), so we'd like to update them to make more sense and be more useful... We'd love to understand your usecases, and how we can make the BuildMaster/Otter Azure integrations great. It'd be quite a bit easier to do this outside of Q&A though, so let's get in touch via email!

This is only available as a legacy action as of 5.2.1; there is no corresponding Operation built for it yet, but we will get one going soon.

The "Generate Release Notes Action" in those release notes was referring to the same action as 4.9.7, which was not implemented in 5.0.0. The Generate Release Notes Operation for v5 plans is available as of v5.2.3.

The current (v4) execution engine does not support Array-type variables, so this would not be possible using that technique. But we will soon (couple weeks) be shipping v4.9, which will include a brand new execution engine, that will include Array/Vector variables, so you could do something like ... foreach $value in @MyVariableList { Transform-Config (...); }

UPDATE: This is supported with the new execution engine, available in BuildMaster 4.9. As of BuildMaster 4.6, this isn't supported, but definitely something we will support in the future. I can see other cases where this would be useful as well (e.g., copying files or deploying artifacts to multiple target servers).

FYI- 4.6.4 has been released, and this fix was included.

Are you sure you're on v4.5.5? This should have been fixed in that version (BM-1685)... it can only happen if you don't have any deployables set up for an application.

This is a known issue having to do with the application & application group filtering of event listeners and was resolved in v4.5.4 (under issue # BM-1675), which was released yesterday - an upgrade will resolve it.

Thanks; we were able to reproduce this, and will revert it to old (correct) behavior in a maintenance release.

SQL patch received and applied, thanks. The Manual action step is now working again. The log file detail shows in the same window using IE but only show as [View Full Log] in Firefox (no new tab or window is opened)

As far as I'm aware, this particular issue has already been resolved. Can you post a new question with the same details? For some quick suggestions though, does echo $ApplicationName work as expected? Is the application configuration to use new variable support (Settings -> Application Settings)?

We don't have export capability for those other items just yet. Does purging the logs as per http://inedo.com/support/questions/1826 not help clean out 90%+ of the space? The log table is the one that typically fills the BuildMaster database. There are some other tables that could also contain a lot of data depending on usage, those being: BuildOutputs (if you generate and store reports with every build) BuildTestResults (if you run unit tests during builds) EventOccurenceDetails & EventOccurences (if many users are constantly using the software) The first 2 can be purged for rejected builds, and the event occurences can be purged entirely if that data is meaningless.

We believe that it should not because it's most likely a mistake to specify a directory that doesn't exist as the working directory since presumably there could be files to work with, etc. in that directory. As you mentioned, the workaround is to create the directory before this step. I would just use mkdir in a PowerShell or Bash script.

Thanks for the bug report, Dave. This has been identified as a regression in 4.2, and will be fixed as BM-1474 in 4.2.6. You can manually visit the page by using the execution ID as a workaround. http://servername:80/executions/view-log?executionId=XXXX

Thank you for the bug report. We have reproduced this and it will be fixed in 4.2.4, which is scheduled for release today. The bug is: BM-1464: NullReferenceException when creating or editing an action where there is a server that the current user does not have access to

In BuildMaster 4.2.0, we are making variables usable across almost all of BuildMaster, including notifiers. If you can wait for the next version, you'll just be able to use a variable in an execution completed notifier. We will likely be shipping a 4.2 beta this week. If you need this functionality before then, you'll have to implement a custom notifier.

We'll be adding some options to control text encoding for the actions which create a text file in 4.1.1, but in the meantime if you want to strip out the byte order marker, it should work to add a Search/Replace File Contents action immediately after the create file action that matches only the created file. Then, enable the Use Regular Expression option and put in a Regex that will match nothing, such as ^$ The Search/Replace action should strip out the characters at the beginning of the file. Alternatively, it would be pretty straightforward to create an alternative Create File action that never writes a BOM using the script repository feature added in BuildMaster 4.1.

Your best bet would be to do a "Delete Files (*) From ~/Src" Action.

Additionally, if you have publish profiles saved in your solution, you can add the following additional argument that will exhibit the same behavior as AutoParameterizationWebConfigConnectionStrings=false for the chosen ProfileName: /p:PublishProfile=ProfileName

Yes; if there is no deployable, then "0" is used as part of the path (e.g. <tmp>\A12\S0\WRK\my-path)