|
|
sponsored by AccuRev
|
|
|
Posted:
|
12 May 2008
|
|
Published:
|
01 May 2008
|
|
Format:
|
PDF
|
|
Length:
|
5
Page(s)
|
|
Type:
|
White Paper
|
|
Language:
|
English
|
|
|
ABSTRACT:
Continuous integration, while not a new concept, has been rapidly adopted as a key technology process in software development organizations as part of the shift towards agile methodologies. Organizations that fail to incorporate this process are unable to improve software quality or reduce costly rework due to broken builds, limiting the business value delivered to end users.
This white paper discusses the concept of continuous integration and outlines several software configuration management (SCM) best practices to consider when implementing continuous integration. Explore the key advantages associated with using an SCM system to store and version all source code. Discover how private developer workspaces help ensure that only well-tested code is accessible to others on the development team. Learn how automated local developer builds ensure the quality of the continuous integration build. Gain insight into the value of establishing a staging and isolation hierarchy.
|
|
|
|
BROWSE RELATED
RESOURCES
Best Practices | Software Configuration Management | Software Development Methodologies | Software Development Tools | Software Quality Assurance | Systems Integration
|
View All Resources
sponsored by AccuRev
|
|
|
|
|
|
TechTarget provides enterprise IT professionals with the information they need to perform their jobs
- from developing strategy, to making cost-effective IT purchase decisions and managing their
organizations' IT projects - with its network of
|
|
|
Definitions:
|
|
 |
|
|
All Rights Reserved,
Copyright 2000 - 2007, TechTarget |
|
|
|
|