Information Technology Reference
In-Depth Information
Labeling a repository version can follow many different styles;
however, the simplest follows this naming pattern:
major release number '_' (or a point, if your CM system accepts
them) minor release number (e.g., 2_89)
Have you ever attempted to deploy software in an environment only to
discover that the environment has a different version of the operating
system, database, or application server? Producing a clean environ-
ment is a matter of removing and reapplying software, scripts, and
configuration values to ensure that the environment is operating as
expected.
When building software, it is critical to ensure that there are no
leftover files or configuration settings that may make the software fail
(or give a false positive). There are different approaches for this. The
first is to start with nothing on the computer and apply a “layer” at a
time until the complete system is applied. This is typically performed
on a testing or staging machine. Ideally, you would automate the
implementation of removing and reapplying each layer. For example,
you would remove everything from a machine and then apply the fol-
lowing layers to it.
• Operating system
• Operating system configurations (e.g., network connectivity,
users, and firewall)
• Server components for the software (e.g., application server,
database server, and messaging server)
• Server configuration
• Third-party tools (such as Web frameworks, object-relational
mapping tool, etc.)
• Custom software (software written for the user)
It's possible to remove only one layer when building the software,
such as the custom software components only. The number of layers
