When I add multiple plans to a pipeline stage, they execute concurrently. Is this the intended behavior, and are there any plans to allow for setting an execution order?

I'm using global plans and global pipelines.

Product: BuildMaster
Version: 5.3.3

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

In BuildMaster 4.9 I could use the procedure dbo.Builds_CreateBuild to trigger a build via SQL code. Running this procedure would do everything necessary to build and promote - in effect, it was the same thing as clicking "New build > Create Build" via the web interface. We used this to trigger large batches of builds programmatically.

In 5.3, that same procedure is not comprehensive and does not trigger the build. Is there a new procedure in 5.3 that has the same comprehensive effect as clicking "Create Package" via the web interface? If not, are there plans to build one, maybe something like dbo.Packages_CreatePackage?

Thanks.

Product: BuildMaster
Version: 5.3.3

Thanks Alana.

Is this the config file and key you are referring to?

c:\BuildMaster\Service\app_appSettings.config

<add key="Core.BaseWorkingDirectory" value="C:\BuildMaster_SVCTMP" />

We use ${ApplicationDirectory} extensively in our scripts. This variable always points to a folder on the C drive. Is it possible to change this to use a different drive letter?

Product: BuildMaster
Version: 4.9.2

Prior to upgrading to v4.8.6 (from 4.8.1) the Active Releases section of the System Overview page showed the most recently build active release for each of our applications. After the upgrade, it shows only older releases. What determines which releases display in this section?

Thanks.

Product: BuildMaster
Version: 4.8.6

I am attempting to run multiple builds concurrently and I am getting errors from the "Get Latest" build step:

svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted

The errors occur when the Build is downloading files from source control.

Is it expected that when using Subversion as a source control provider, the same working folder will be used, regardless of which application is executing the build?

The working folder that is being used is C:\BuildMaster_SVCTMP\SrcRepos<repository name>_

Product: BuildMaster
Version: 4.8.1