Continuous Integration
Improving Software Quality and Reducing Risk
(Sprache: Englisch)
When more than one person works on a software project there is a need for a merging or integration of the parts of the project to develop the whole. With this merging, there are problems (one of the largest being bugs are introduced). The practice of...
lieferbar
versandkostenfrei
Buch (Kartoniert)
Fr. 64.90
inkl. MwSt.
- Kreditkarte, Paypal, Rechnungskauf
- 30 Tage Widerrufsrecht
Produktdetails
Produktinformationen zu „Continuous Integration “
Klappentext zu „Continuous Integration “
When more than one person works on a software project there is a need for a merging or integration of the parts of the project to develop the whole. With this merging, there are problems (one of the largest being bugs are introduced). The practice of Continuous Integration (CI) looks to reduce these problems by testing and running what is referred to as a "build" on a daily basis, to evaluate the software as a whole. Using plenty of examples in Java and .NET, this book focuses on the practices and then covers how to use them. As the reader works their way through the book they will learn: --Patterns and Techniques for creating an effective CI system --How implementing CI will make software projects more efficient and manageable --How a CI platform can facilitate the implementation of software engineering practices --Pitfalls in using a CI platform The book is split into three parts so whether the reader has never read about CI before, has used the basics, or has been doing CI for years, there is wisdom and practical techniques for everyone.
Inhaltsverzeichnis zu „Continuous Integration “
Foreword by Martin Fowler xiiiForeword by Paul Julius xvPreface xixAbout the Authors xxxiAbout the Contributors xxxiiiPart I: A Background on CI: Principles and Practices 1Chapter 1: Getting Started 3 Build Software at Every Change 4
Features of CI 12
Summary 20
Questions 20Chapter 2: Introducing Continuous Integration 23
A Day in the Life of CI 25
What Is the Value of CI? 29
What Prevents Teams from Using CI? 32
How Do I Get to Continuous Integration? 33
When and How Should a Project Implement CI? 35
The Evolution of Integration 36
How Does CI Complement Other Development Practices? 37
How Long Does CI Take to Set Up? 38
CI and You 39
Commit Code Frequently 39
Don't Commit Broken Code 41
Fix Broken Builds Immediately 41
Write Automated Developer Tests 41
All Tests and Inspections Must Pass 42
Run Private Builds 42
Avoid Getting Broken Code 43
Summary 44
Questions 44Chapter 3: Reducing Risks Using CI 47
Risk: Lack of Deployable Software 49
Risk: Late Discovery of Defects 53
Risk: Lack of Project Visibility 55
Risk: Low-Quality Software 57
Summary 62
Questions 62Chapter 4: Building Software at Every Change 65
Automate Builds 67
Perform Single Command Builds 69
Separate Build Scripts from Your IDE 73
Centralize Software Assets 74
Create a Consistent Directory Structure 75
Fail Builds Fast 76
Build for Any Environment 77
Build Types and Mechanisms 78
Use a Dedicated Integration Build Machine 81
Use a CI Server 85
Run Manual Integration Builds 86
Run Fast Builds 87
Stage Builds 92
How Will This Work for You? 96
Summary 101
Questions 102Part II: Creating a Full-Featured CI
... mehr
System 105Chapter 5: Continuous Database Integration 107
Automate Database Integration 110
Use a Local Database Sandbox 117
Use a Version Control Repository to Share Database Assets 119
Continuous Database Integration 121
Give Developers the Capability to Modify the Database 123
The Team Focuses Together on Fixing Broken Builds 124
Make the DBA Part of the Development Team 124
Database Integration and the Integrate Button 125
Summary 126
Questions 128Chapter 6: Continuous Testing 129
Automate Unit Tests 132
Automate Component Tests 134
Automate System Tests 136
Automate Functional Tests 137
Categorize Developer Tests 138
Run Faster Tests First 141
Write Tests for Defects 143
Make Component Tests Repeatable 148
Limit Test Cases to One Assert 156
Summary 158
Questions 159Chapter 7: Continuous Inspection 161
What Is the Difference between Inspection and Testing? 164
How Often Should You Run Inspectors? 165
Code Metrics: A History 166
Reduce Code Complexity 167
Perform Design Reviews Continuously 170
Maintain Organizational Standards with Code Audits 173
Reduce Duplicate Code 176
Assess Code Coverage 180
Evaluate Code Quality Continuously 182
Summary 185
Questions 186Chapter 8: Continuous Deployment 189
Release Working Software Any Time, Any Place 191
Label a Repository's Assets 191
Produce a Clean Environment 194
Label Each Build 195
Run All Tests 196
Create Build Feedback Reports 196
Possess Capability to Roll Back Release 199
Summary 199
Questions 200Chapter 9: Continuous Feedback 203
All the Right Stuff 205
Use Continuous Feedback Mechanisms 209
Summary 222
Questions 222Epilogue: The Future of CI 223Appendix A: CI Resources 227
Continuous Integration Web Sites/Articles 227
CI Tools/Product Resources 229
Build Scripting Resources 232
Version Control Resources 233
Database Resources 234
Testing Resources 236
Automated Inspection Resources 239
Deployment Resources 241
Feedback Resources 241
Documentation Resources 243Appendix B: Evaluating CI Tools 245
Considerations When Evaluating Tools 247
Automated Build Tools 255
Build Scheduler Tools 263
Conclusion 272Bibliography 273Index 275
Automate Database Integration 110
Use a Local Database Sandbox 117
Use a Version Control Repository to Share Database Assets 119
Continuous Database Integration 121
Give Developers the Capability to Modify the Database 123
The Team Focuses Together on Fixing Broken Builds 124
Make the DBA Part of the Development Team 124
Database Integration and the Integrate Button 125
Summary 126
Questions 128Chapter 6: Continuous Testing 129
Automate Unit Tests 132
Automate Component Tests 134
Automate System Tests 136
Automate Functional Tests 137
Categorize Developer Tests 138
Run Faster Tests First 141
Write Tests for Defects 143
Make Component Tests Repeatable 148
Limit Test Cases to One Assert 156
Summary 158
Questions 159Chapter 7: Continuous Inspection 161
What Is the Difference between Inspection and Testing? 164
How Often Should You Run Inspectors? 165
Code Metrics: A History 166
Reduce Code Complexity 167
Perform Design Reviews Continuously 170
Maintain Organizational Standards with Code Audits 173
Reduce Duplicate Code 176
Assess Code Coverage 180
Evaluate Code Quality Continuously 182
Summary 185
Questions 186Chapter 8: Continuous Deployment 189
Release Working Software Any Time, Any Place 191
Label a Repository's Assets 191
Produce a Clean Environment 194
Label Each Build 195
Run All Tests 196
Create Build Feedback Reports 196
Possess Capability to Roll Back Release 199
Summary 199
Questions 200Chapter 9: Continuous Feedback 203
All the Right Stuff 205
Use Continuous Feedback Mechanisms 209
Summary 222
Questions 222Epilogue: The Future of CI 223Appendix A: CI Resources 227
Continuous Integration Web Sites/Articles 227
CI Tools/Product Resources 229
Build Scripting Resources 232
Version Control Resources 233
Database Resources 234
Testing Resources 236
Automated Inspection Resources 239
Deployment Resources 241
Feedback Resources 241
Documentation Resources 243Appendix B: Evaluating CI Tools 245
Considerations When Evaluating Tools 247
Automated Build Tools 255
Build Scheduler Tools 263
Conclusion 272Bibliography 273Index 275
... weniger
Autoren-Porträt von Paul Duvall
Paul Duvall is the CEO of Stelligent, a firm that helps clients create production-ready software every day. A featured speaker at many leading software conferences, he has worked in virtually every role on software projects: developer, project manager, architect, and tester. He is the principal author of Continuous Integration: Improving Software Quality and Reducing Risk (Addison-Wesley, 2007), a 2008 Jolt Award Winner. Paul contributed to the UML 2 Toolkit (Wiley, 2003), writes a series for IBM developerWorks called Automation for the people, and contributed a chapter to No Fluff Just Stuff Anthology: The 2007 Edition (Pragmatic Programmers, 2007). He is passionate about automating software development and release processes and actively blogs on IntegrateButton.com and TestEarly.com. Stephen M. Matyas III is vice president of AutomateIT, a service branch of 5AM Solutions. He has a varied background in applied software engineering, with much of his professional, hands-on experience being in the areas of enterprise Java and custom software development and services.
Andrew Glover, president of Stelligent Incorporated, is a frequent speaker at conferences throughout North America, as well as author and coauthor of many books and online articles.
Bibliographische Angaben
- Autor: Paul Duvall
- 2007, 336 Seiten, mit Abbildungen, Masse: 23,3 x 17,7 cm, Kartoniert (TB), Englisch
- Verlag: Addison-Wesley Longman, Amsterdam
- ISBN-10: 0321336380
- ISBN-13: 9780321336385
- Erscheinungsdatum: 29.06.2007
Sprache:
Englisch
Kommentar zu "Continuous Integration"
0 Gebrauchte Artikel zu „Continuous Integration“
| Zustand | Preis | Porto | Zahlung | Verkäufer | Rating |
|---|
Schreiben Sie einen Kommentar zu "Continuous Integration".
Kommentar verfassen