Deployment Builder Version 1.0.322 Released

The Deployment Builder is designed to be used in an enterprise environment that utilizes a SDLC procedure. Specifically this means that only authorized users should be granted permission to deploy to an environment. This security restriction is extended to all application environments: development, quality, user acceptance testing (known as staging for some) and production.

The security policies are enforced using two layers of security. First the appropriate roles must be granted to a user in order to gain access to the application. The predefined roles grant access ranging from a read-only audit role, to a full system administrator role. The second layer of security uses a shared deployment password. Each of the environments mentioned above, will have its own password used during the deployment process.

As an example the quality environment will have its own deployment password. Presuming that only users in the QA group are allowed to modify that environment, the QA group should be the only group that knows the QA deployment password. For an extra measure of protection from auditors that know system administrators can look at the database for the password, the deployment passwords are hashed before they are stored.

For those that have to contend with the additional complexities of Sarbanes-Oxley compliance, the Deployment Builder can assist with (but not guarantee) compliance. Every step during the deployment process is logged in both a log file and the database. Deployment Builder will report what it is doing and what is changing while it is changing it.

It is important to note that since every environment is very different, a lot of configuration is required ahead of time before Deployment Builder can be used or evaluated. This application will not work "out of the box". Please see the wiki on how to properly install and configure Deployment Builder.

Special thanks to Rob Brooks-Bilson and Adam Crump for providing the time and encouragement to open source this application.

Requirements:
ColdFusion 7 or 8 (6 should work but has not been tested)
SQL Server 2000 or 2005 (2005 Express works too)
Mach II 1.5
ColdSpring
Ext 2
Java SE 6
Apache ANT 1.7.0
Library Dependencies for ANT FTP task
SVN Client
FTP Server

Please let me know how this application works for you and if you have any suggestions.

Thanks,

Matt Riley