Find a copy online
Links to this item
Find a copy in the library
Finding libraries that hold this item...
|Additional Physical Format:||Print version:
Continuous Delivery and DevOps : A Quickstart guide.
Birmingham : Packt Publishing, ©2012
|Material Type:||Document, Internet resource|
|Document Type:||Internet Resource, Computer File|
|All Authors / Contributors:||
|ISBN:||9781849693691 1849693692 1849693684 9781849693684|
|Description:||1 online resource (136 pages) : illustrations|
|Contents:||Table of Contents; Continuous Delivery and DevOps: A Quickstart Guide; Continuous Delivery and DevOps: A Quickstart Guide; Credits; About the Author; Acknowledgement; About the Reviewers; www.PacktPub.com; Support files, eBooks, discount offers and more; Why Subscribe?; Free Access for Packt account holders; Preface; What this book covers; What you need for this book; Who this book is for; Conventions; Reader feedback; Customer support; Errata; Piracy; Questions; 1. Evolution of a Software House; ACME systems Version 1.0; Software delivery process flow Version 1.0; ACME systems Version 2.0. Software delivery process flow Version 2.0A few brave men and women; ACME systems Version 3.0; Software delivery process flow Version 3.0; Summary; 2. No Pain, No Gain; Elephant in the room; Ground rules; Openness and honesty is the key; Include (almost) everyone; Some tried and tested techniques; Value stream mapping; Using retrospectives; The timeline game; StoStaKee; Summary; 3. Plan of Attack; Setting and communicating goals and vision; Standardizing vocabulary and language; A business change project in its own right; The benefits of a dedicated team; The importance of evangelism. The courage and determination required throughout the organizationUnderstanding the cost; Seeking advice from others; Summary; 4. Tools and Technical Approaches; Engineering best practice; Source control; Small, frequent, and simple changes; Never break your consumer; Open and honest peer working practices; Fail fast and often; Automated build and testing; Continuous integration; Architectural approaches; Component based architecture; Layers of abstraction; How many environments is enough?; Using the same binary across all environments; Develop against a like live environment; CD tooling. Automated provisioningNo-downtime deployments; Monitoring; When a simple manual process is also an effective tool; Summary; 5. Culture and Behaviors; Open, honest, and courageous dialogue; Openness and honesty; Courageous dialogue; The physical environment; Encouraging and embracing collaboration; Fostering innovation and accountability at grass roots; The blame culture; Blame slow, learn quickly; Building trust-based relationships across organizational boundaries; Rewarding good behaviors and success; The odd few; Recognizing how different teams are incentivized can have an impact. Embracing change and reducing riskChanging people's perceptions with pudding; Being highly visible about what you are doing and how you are doing it; Summary; 6. Hurdles to Look Out For; What are the potential issues you need to look out for?; Dissenters in the ranks; The change curve; The outsiders; Corporate guidelines, red tape, and standards; Geographically diverse teams; Failure during the evolution; Processes that are not repeatable; Recruitment; Summary; 7. Measuring Success and Remaining Successful; Measuring effective engineering best practice; Code versus comments; Code complexity.|
- Computer software -- Development.
- Computer software -- Reliability.
- COMPUTERS -- Computer Literacy.
- COMPUTERS -- Computer Science.
- COMPUTERS -- Data Processing.
- COMPUTERS -- Hardware -- General.
- COMPUTERS -- Information Technology.
- COMPUTERS -- Machine Theory.
- COMPUTERS -- Reference.
- Computer software / Development.
- Computer software / Reliability.