Continuous integration (Continuous Integration: Improving Software Quality and Reducing Risk)
Continuing the theme of rare books on engineering processes in software development (beginning here)I decided to recall this book by Andrew Glover, Paul Duval and Stephen Mathias. In short, a good book was for its time. (2007 year). It’s worth reading now just to find out where it all started. However, if it is updated, the book will be good again. In more detail, the author describes some practices that have become basic at the present time:
- What is CI and how it helps in software development, namely in reducing risks: Problem with deployment n ("It works on my car.") late detection of defects, and therefore more expensive correction Poor monitoring of project status (It is not clear what is ready and what is not.)
- poor product quality (presence of a large number of bugs)
- What is required to implement CI
- storage of source in the version control system Storage of configurations in the version control system (SCM) Storage of changes for BD in the version control system (data migration) The possibility of putting it all together.(smile)
The authors also consider the creation of a fully functional CI, although in the realities of fifteen years ago. This part is completely outdated, but even in it there are interesting points:
- Discussion of testing issues:
- unit
- functional
- integration
- system
- code inspection
- use of static analyzers Support for code style Support for code metrics at a given level, such as cyclomatic complexity
- organization of continuous delivery
- feedback on the work of CI
In general, at the moment, the book should be read only to feel nostalgia for those times when the development was carried out on the knee:)
#Devops #ContinuousDelivery #Software #SoftwareDevelopment #ContinuousIntegration