Practical DevOps harness the power of DevOps to boost your skill set and make your IT organization perform better
Harness the power of DevOps to boost your skill set and make your IT organization perform better About This Book Get to know the background of DevOps so you understand the collaboration between different aspects of an IT organization and a software developer Improve your organization's performa...
| Otros Autores: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Birmingham :
Packt Publishing
2016.
|
| Edición: | 1st edition |
| Colección: | Community experience distilled.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009630069006719 |
Tabla de Contenidos:
- Cover ; Copyright; Credits; About the Author; About the Reviewers; www.PacktPub.com; Table of Contents; Preface; Chapter 1: Introduction to DevOps and Continuous Delivery ; Introducing DevOps; How fast is fast?; The Agile wheel of wheels; Beware the cargo cult Agile fallacy; DevOps and ITIL; Summary; Chapter 2: A View from Orbit ; The DevOps process and Continuous Delivery - an overview; The developers; The revision control system; The build server; The artifact repository; Package managers; Test environments; Staging/production; Release management; Scrum, Kanban, and the delivery pipeline
- Wrapping up - a complete exampleIdentifying bottlenecks; Summary; Chapter 3: How DevOps Affects Architecture ; Introducing software architecture; The monolithic scenario; Architecture rules of thumb; The separation of concerns; The principle of cohesion; Coupling; Back to the monolithic scenario; A practical example; Three-tier systems; The presentation tier; The logic tier; The data tier; Handling database migrations; Rolling upgrades; Hello world in Liquibase; The changelog file; The pom.xml file; Manual installation; Microservices; Interlude - Conway's Law
- How to keep service interfaces forward compatibleMicroservices and the data tier; DevOps, architecture, and resilience; Summary; Chapter 4: Everything is Code ; The need for source code control; The history of source code management; Roles and code; Which source code management system?; A word about source code management system migrations; Choosing a branching strategy; Branching problem areas; Artifact version naming; Choosing a client; Setting up a basic Git server; Shared authentication; Hosted Git servers; Large binary files; Trying out different Git server implementations
- Docker intermissionGerrit; Installing the git-review package; The value of history revisionism; The pull request model; GitLab; Summary; Chapter 5: Building the Code ; Why do we build code?; The many faces of build systems; The Jenkins build server; Managing build dependencies; The final artifact; Cheating with FPM; Continuous Integration; Continuous Delivery; Jenkins plugins; The host server; Build slaves; Software on the host; Triggers; Job chaining and build pipelines; A look at the Jenkins filesystem layout; Build servers and infrastructure as code; Building by dependency order
- Build phasesAlternative build servers; Collating quality measures; About build status visualization; Taking build errors seriously; Robustness; Summary; Chapter 6: Testing the Code ; Manual testing; Pros and cons with test automation; Unit testing; JUnit in general and JUnit in particular; A JUnit example; Mocking; Test Coverage; Automated integration testing; Docker in automated testing; Arquillian; Performance testing; Automated acceptance testing; Automated GUI testing; Integrating Selenium tests in Jenkins; JavaScript testing; Testing backend integration points; Test-driven development
- REPL-driven development
