|
Continuous Integration and Enterprise Build Automation How often have you or one of your teammates checked the source code into the code library which then instantly triggered an automated build? How many times did this instant build succeed? Do you have an automated build and release system that ensures your software is built in the same way each and every time? Are deployments to staging environments entirely automated and executed with a single click? While reviewing a defect in a production release, are you able to backtrack through the source code changes and identify the root cause of failure? If the last good checkin happened a few days ago, identification of this root cause of failure would become even more difficult. Seasoned CM practitioners advise that you perform a daily build to avoid such integration issues. What an irony it is that only a few projects take advantage of this simple, yet powerful technique known as Continuous Integration (CI).
|
|
|
Tool Integration In Distributed Agile Development This article provides an overview of various tools, integration strategies and their benefits in agile environments. These tools would come in handy in implementing key agile practices like daily builds, refactoring, continuous integration and test driven development.
|
|
|
How to Implement Continuous Integration The term “continuous integration” is getting a bit of attention these days. It refers to the process of integrating often (or immediately) to reduce integration effort, complexity, and pain.It allows for others make changes more readily. While the term “continuous” is catchy, it is not accurate in what the concept implies. In context to integration, it implies a process without interruption.
|
|
|
Agile Build Promotion: Navigating the Ocean of Promotion Notions In this article Brad Appleton delves into the realm of build status accounting to discuss various build promotion models and how to choose an appropriate and effective implementation of a build promotion lifecycle.
|
|
|
Approaching Parallel Development with Branch - Merge Strategies Many times when managers first consider parallel development, it appears to be a very effective way to manage changes to concurrent streams of development. This is somewhat true if the project uses an SCM technology that allows for stable branching and establishes discreet project and maintenance branches. However, what is often forgotten is that while branching is a great way to separate code changes, at some point merging will have to occur. This article provides guidance for approaching and performing parallel development.
|
|