EmbMap | ContinuesIntegration / CIInPracticeAndInvestigation

CI in Practice and Investigation

Automation for the people (Paul Duvall, IBM developerWorks) series essays: quite inspiring articles there, below are some of them, that're related to CI topics:
- Automation for the people: Continuous Integration anti-patterns, Part 1
- Automation for the people: Continuous Integration anti-patterns, Part 2 - Summary: While Continuous Integration (CI) can be extremely effective at reducing risks on a project, it requires a greater emphasis on your day-to-day activities related to coding. In these two-part articles in the Automation for the people series, automation expert and co-author of Continuous Integration: Improving Software Quality and Reducing Risk, Paul Duvall, lays out a series of CI anti-patterns, and more importantly, shows how to avoid them.
- Automation for the people: Continuous testing - Summary: Ready to step up to the plate and hit a home run with your developer testing activities? In this installment of Automation for the people, development automation expert Paul Duvall covers some of the various types of automated developer tests you can run with every source code change. Paul provides examples of Selenium, DbUnit, and JUnitPerf tests that can help you discover application problems early -- that is, if they're run often.
- Automation for the people: Choosing a Continuous Integration server - Summary: With so many Continuous Integration (CI) servers to choose from, it can be difficult to decide which one is right for you. In the second article of the series Automation for the people, development automation expert Paul Duvall looks at a handful of open source CI servers, including Continuum, CruiseControl, and Luntbuild, using a consistent evaluation criteria and illustrative examples.
- Automate your team's build and unit-testing process - Summary: Extreme programming and agile methods recommend that the development process include continuous integration and unit testing. A pragmatic way to support these practices is to set up an automated system to build and test the latest version of your source code every time it changes. This article guides you through the practical issues involved in setting up your own Linux™-based build server for Java™ projects.
- Automation for the people: Continuous feedback - Summary: Feedback is vital for the practice of Continuous Integration (CI) -- in fact, it's the life blood of a CI system. Rapid feedback enables speedy responses to build events that require attention. Without feedback mediums like e-mail or RSS, builds in a broken state have the tendency to stay broken, which defeats the purpose of CI in the first place! In this installment of Automation for the people, automation expert Paul Duvall examines various feedback mechanisms that you can incorporate into CI systems.
Realizing continuous integration - Kevin A. Lee, Technical Consultant, IBM

The Most Frequent Refered Resources about Continues Integration

Continuous Integration - by Martin Fowler and Matthew Foemmel
Continuous integration - description at Wikipedia
Multi-stage continuous integration - description at Wikipedia
CITCON, the Continuous Integration and Testing Conference - CITCON is a world-wide series of free Open Spaces events for developer-testers, tester-developers and anyone else with an interest in Continuous Integration and the type of Testing that goes along with it.
CruiseControl Official Site
CI Frameworks & Tools - CI Frameworks & Tools List

粤ICP备07005877号