Drawing the Line: Continuous Integration and Build Management
The purpose of Build Management is very different from that of Continuous Integration. Build Management, essentially, aims to produce a set of artifacts that correspond to a specified snapshot of source code, and to be able to hand off those artifacts to third parties outside of development. In this regard, the purpose of Build Management is really all about producing the run-time artifacts. This is key, as it is senseless to hand off source code to QA, management, or production.
| DOWNLOAD NOW | |||||
| Publisher: | Urbancode | Published: | 12/03/2008 | Type: Length: Format: |  Whitepaper 9 pages |
| Rating: | Share: | Send to a friend | |||
| Topics: | Integration | ||||
Related Library Resources
01/19/2009 Essential Requirements for Authorization/Entitlements Management
04/15/2009 Memory Analysis Best Practices Within Eclipse
02/15/2009
SOA Governance
12/31/2008 The Websese ThreatSeeker Network: Leveraging Websense HoneyGrid Computing
08/07/2008 BPEL Basics for Java Developers
09/26/2008 Six Steps to Signing your Java Code
09/05/2008 Fixing and Finding Troublesome Long Running Ingres Queries
09/17/2008 Top 10 Secrets for DBA Career Success
03/01/2009 Scalability & High Availability
09/10/2008 MapQuest Platform: Enterprise Edition
Spotlight Resources
Essential EMF
The Eclipse Modeling Framework (EMF) is a powerful framework and code generation facility for building Java applications based on simple model...
Core Mule
Mule is one of the most mature open source enterprise service busses (ESBs) out there. It provides an easy to use, lightweight ESB that can easily...
Getting Started with Equinox and OSGi
Equinox is a highly modular, dynamic Java runtime environment based on the OSGi framework specifications. This reference card gives you a quick...
Want your resource here? Contact our team today.
