|
The best indicator of software development success is working code. This is an idea that extends beyond specific Agile software development methods — more and more teams, from ISVs to enterprise IT teams, are recognizing the benefits of integrating early and often. But tool and process improvements in the build and release cycle are absolutely critical to realizing that goal.
To a build manager or team lead, the words 'multiple integrations per day' and 'Continuous Integration' mean a radical change from once-nightly (or even less frequent) build and test cycles. Adopting Continuous Integration or other agile build and test techniques require fast, highly automated builds and tests and integration between source control and the build system.
Further, Continuous Integration can actually slow development and hurt quality in an enterprise environment by introducing frequently broken builds. So providing developers with the ability to build and test on production-class machines (not just their local system) before checking in code, so-called preflight builds and tests, is essential.
There are ways to develop some build automation capabilities on your own, but most homegrown approaches are inherently brittle and require ongoing maintenance.
Learn more about how ElectricCommander, ElectricAccelerator, and ElectricInsight automate, accelerate, and analyze agile build and release processes.
|