Once a build has been promoted to an environment, its Deployment Plan may be
executed for that environment. Because applications exist in multiple
environments, each an application will have a different deployment plan for each
environment it participates in.
A Deployment Plan describes the steps necessary to deploy an application to
an environment. Regardless of their technology, platform, or purpose, all
software applications are deployed to a target environment in the same manner:
- Source Preparation – the various source files required for
compilation of the application are consolidated from different repositories
(source control, file systems, etc) into a central location.
- Compilation – the source files are transformed into the application
files, which could involve compiling source code to executables, compressing
files into more manageable files, etc.
- Shutdown – the currently running application is stopped in the
target environment; this could involve shutting down a service/daemon or
stopping an application server.
- Installation – the application files created in the Compilation
step are installed in the appropriate folders on the target server(s).
- Start-up – with the new files in place, the application is
In BuildMaster, each plan consists of one or more Action Groups, each which
consist of one or more Actions. An Action represents a discrete step – getting
latest from source control, compiling an executable, transferring files to a
different folder, etc – that is required in order to deploy.
This content has the following tags: