Deploy Configuration File according to server environment

[Jason Smoliak]

One of the more powerful improvements to the latest Buildmaster is the relationship between pipelines and deployment plans. It dramatically simplifies things here at TLG for code deployment orchestration.

I'm able to deploy webcode in a deployment plan and allow the pipeline configuration decide where it needs to go based on what environment stage I'm in.

I'm wondering if this also extends to configuration variables.

For example, my aforementioned scenario of webcode and pipeline stages might have the set of stages {dev,qa,staging,production}. An application using that pipeline could have a deployment file called example.config with the set of environments {dev,qa,staging,production} (the same as the pipeline).

Can I call a 'deploy config file' action and let the pipeline stage and associated environment pick the corresponding config file instance?

This feature would really bring the end-to-end deployment process full circle for our organization!

Product: BuildMaster
Version: 5.6.8

[Tod]

Are you referring to the Configuration Files stored in the Assets portion of the application? If so, as long as the instance name of the configuration files matches the environment name set in the pipeline stage... the following operation should do what you want:

Deploy-ConfigFile
(
    ConfigFileName: example.config,
    Instance: $EnvironmentName,
    To: E:\Path\to\targetDir
);

[Jason Smoliak]

This is exactly what I was looking for, thank you!