Buildmaster Database Connection Variable

[Jason Smoliak]

I'm wondering if it's possible to wrap sql change scripts into a "for each" environment loop, in the same way that is implicitly done with servers

e.g. define database connections: dev, qa, staging, prod;

Dev deployment plan would look like:

for each "sql change script"
Execute for db connection in {Current_Environment}

Product: BuildMaster
Version: 5.7.3

[Ben Lubar]

Hello Jason,

I've filed [BM-3081], which will allow you to do this:

foreach $ConnectionName in @DatabaseConnectionsInEnvironment($EnvironmentName)
{
    Execute-ChangeScripts
    (
        Connection: $ConnectionName
    );
}

The default value for environmentName is the current environment ($EnvironmentName), so you can also just call @DatabaseConnectionsInEnvironment() with no argument (once this is released).