BuildMaster allows you to store, manage, and deploy configuration files associated with your applications. Configuration files are managed per-application and are instanced, allowing for differing configurations per-environment. Since restrictions and privileges can also be scoped per-environment, this allows for the protection of sensitive information that may be within your configuration files like passwords.
For explicit instruction on how to add and manage configuration files, see Step four of the Getting Started with BuildMaster tutorial.
Configuration templates allow you to reuse common configurations across different applications. Using templating allows for one of the following transformations to occur automatically when an instance is deployed:
None - Configuration file instances are deployed with no additional transformations.
Key/Value Pairs - Configuration file instances contain lines with simple key/value pairs in the format:
The key/value pairs are treated like additional variables to replace in the specified template instance. A common use for this would be for deploying to multiple environments, such as ProductionA and ProductionB.
XSLT - Configuration file instances are transformed by an XSLT transform defined in the specified template instance.
Configuration files can be deployed either manually or as part of a deployment plan Each instance is deployed to a specific path on a server, using either its default file name or a user-specified file name.
BuildMaster has two built-in operations for configuration files: Deploy Configuration File and Export Configuration File. These operations may be added and executed through a deployment plan. Once the configuration file is deployed (manually or as a part of a plan), BuildMaster will record any file changes that occurred during the deployment.