Cargando…
Continuous Integration vs. Continuous Delivery vs. Continuous Deployment, 2nd Edition /
Continuous integration, continuous delivery, and continuous deployment are key software delivery processes in a DevOps environment. But what does each one do for your product development and release cycles? In this updated report, Brent Laster explains what these terms really boil down to and how th...
| Autor principal: | |
|---|---|
| Autor Corporativo: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
O'Reilly Media, Inc.,
2020.
|
| Edición: | 2nd edition. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a22000007a 4500 | ||
|---|---|---|---|
| 001 | OR_on1162605817 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr cnu|||||||| | ||
| 008 | 200701s2020 xx o 000 0 eng | ||
| 040 | |a AU@ |b eng |c AU@ |d ERF |d OCLCQ |d TOH |d OCLCQ | ||
| 020 | |z 9781492088936 | ||
| 024 | 8 | |a 9781492088943 | |
| 029 | 0 | |a AU@ |b 000067299661 | |
| 035 | |a (OCoLC)1162605817 | ||
| 049 | |a UAMI | ||
| 100 | 1 | |a Laster, Brent, |e author. | |
| 245 | 1 | 0 | |a Continuous Integration vs. Continuous Delivery vs. Continuous Deployment, 2nd Edition / |c Laster, Brent. |
| 250 | |a 2nd edition. | ||
| 264 | 1 | |b O'Reilly Media, Inc., |c 2020. | |
| 300 | |a 1 online resource (20 pages) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 347 | |a text file | ||
| 520 | |a Continuous integration, continuous delivery, and continuous deployment are key software delivery processes in a DevOps environment. But what does each one do for your product development and release cycles? In this updated report, Brent Laster explains what these terms really boil down to and how they work separately and together to help your team release software. This powerful set of disciplines, best practices, and technologies automates the integration and delivery of source code changes from inception through production. Although their implementation may vary, continuous integration, continuous delivery, and continuous deployment are necessary to ensure that software is released frequently, reliably, and with high quality. You'll learn how: Continuous integration makes certain that individual code changes are suitable for inclusion in the code base and merged in successfully Continuous delivery assembles your product, automatically tests quality and functionality, and produces deliverables that are proven to be deployable Continuous deployment simplifies releasing the product to customers-whether it's in the cloud, via download, or in some other format-while also allowing for limited deployments or rolling deployments back This valuable resource for business professionals, software engineering managers, senior developers, and architects will also explore how containers and Kubernetes interact in this environment. | ||
| 542 | |f Copyright © 2020 O'Reilly Media, Inc. | ||
| 550 | |a Made available through: Safari, an O'Reilly Media Company. | ||
| 588 | |a Online resource; Title from title page (viewed July 25, 2020) | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 1 | 4 | |a Software de aplicación. |
| 650 | 2 | 4 | |a Libros electrónicos. |
| 710 | 2 | |a Safari, an O'Reilly Media Company. | |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/9781492088943/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 936 | |a BATCHLOAD | ||
| 994 | |a 92 |b IZTAP | ||