PortadaGruposSe habla deMásVisión actual
Buscar En Este Sitio
Este sitio utiliza cookies para ofrecer nuestros servicios, mejorar el rendimiento, para análisis y (si no está registrado) para publicidad. Al usar LibraryThing reconoces que has leído y comprendido nuestros Términos de Servicio y Política de Privacidad. Su uso del sitio y de los servicios está sujeto a estas políticas y términos.
Hide this

Resultados de Google Books

Pulse en una miniatura para ir a Google Books.

Continuous Delivery: Reliable Software…
Cargando...

Continuous Delivery: Reliable Software Releases through Build, Test, and… (edición 2010)

por Jez Humble (Autor)

MiembrosReseñasPopularidadValoración promediaConversaciones
292468,678 (3.85)Ninguno
Winner of the 2011 Jolt Excellence Award! Getting software released to users is often a painful, risky, and time-consuming process. This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-- sometimes even minutes-no matter what the size of a project or the complexity of its code base.   Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the "deployment pipeline," an automated process for managing all changes, from check-in to release. Finally, they discuss the "ecosystem" needed to support continuous delivery, from infrastructure, data and configuration management to governance.   The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes   * Automating all facets of building, integrating, testing, and deploying software * Implementing deployment pipelines at team and organizational levels * Improving collaboration between developers, testers, and operations * Developing features incrementally on large and distributed teams * Implementing an effective configuration management strategy * Automating acceptance testing, from analysis to implementation * Testing capacity and other non-functional requirements * Implementing continuous deployment and zero-downtime releases * Managing infrastructure, data, components and dependencies * Navigating risk management, compliance, and auditing   Whether you're a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever--so you can deliver value to your business rapidly and reliably.  … (más)
Miembro:hustlergate
Título:Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler))
Autores:Jez Humble (Autor)
Info:Addison-Wesley Professional (2010), Edition: 1, 512 pages
Colecciones:Continuous Integration & Deployment, Tu biblioteca
Valoración:
Etiquetas:Ninguno

Detalles de la obra

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation por Jez Humble

Ninguno
Cargando...

Inscríbete en LibraryThing para averiguar si este libro te gustará.

No hay Conversaciones actualmente sobre este libro.

Mostrando 4 de 4
It really provides quality content. However giving it 4 star as I find the content can be organized in more concise and optimal way. You will read the same information over and over, several times, which I think makes harder to focus on new material. ( )
  Tornike.Zedginidze | Nov 6, 2016 |
I'm a bit torn on this book: on the one hand, it is a very thorough look at a number of important, but often overlooked topics; on the other hand, the book is not a very effective teacher of this important material. The biggest problem is the lack of real world examples. Chapters are mostly huge blocks of advice: the advice is good, but not memorable or actionable in the way it is presented. There need to be far more examples of real world systems with both good approaches and bad approaches discussed and compared in detail.

Moreover, the book is very very repetitive. Perhaps it's from an attempt to make each chapter standalone, but while trying to find the new and interesting info in a new chapter, you have to wade through tons of info you read many times in earlier chapters (or even earlier paragraphs). There are many sentences, paragraphs, and even pages that can be skipped because they are obvious or just a rehash of something earlier (or both).

In short, this is a VERY important - perhaps even required - read for anyone working on medium and large software projects, but this book desperately needs a tldr companion with lots of examples.

A few good quotes from the book:

If It Hurts, Do It More Frequently, and Bring the Pain Forward

Done Means Released

In our experience, it is an enduring myth that configuration information is somehow less risky to change than source code.

Without continuous integration, your software is broken until somebody proves it works, usually during a testing or integration stage. With continuous integration, your software is proven to work (assuming a sufficiently comprehensive set of automated tests) with every new change—and you know the moment it breaks and can fix it immediately.

For the software delivery process, the most important global metric is cycle time. This is the time between deciding that a feature needs to be implemented and having that feature released to users. As Mary Poppendieck asks, “How long would it take your organization to deploy a change that involves just one single line of code? Do you do this on a repeatable, reliable basis?”

Errors are easiest to fix if they are detected early, close to the point where they were introduced.

To paraphrase, performance is a measure of the time taken to process a single transaction, and can be measured either in isolation or under load. Throughput is the number of transactions a system can process in a given timespan. It is always limited by some bottleneck in the system. The maximum throughput a system can sustain, for a given workload, while maintaining an acceptable response time for each individual request, is its capacity. Customers are usually interested in throughput or capacity.

When we talk about components, we mean a reasonably large-scale code structure within an application, with a well-defined API, that could potentially be swapped out for another implementation. A component-based software system is distinguished by the fact that the codebase is divided into discrete pieces that provide behavior through well-defined, limited interactions with other components. ( )
  brikis98 | Nov 11, 2015 |
Not bad, honestly, but I expected more. I think that if you've already engaged with delivery systems and worked through the issues on a few projects, you could probably take a pass on this one, although it's a decent enough primer. I'd probably like it more if I'd read it earlier in my career. ( )
  sdmouton | May 19, 2015 |
Lots of sound, if sometimes redundant, advice. ( )
1 vota ludovicofischer | Dec 18, 2011 |
Mostrando 4 de 4
sin reseñas | añadir una reseña

Belongs to Publisher Series

Debes iniciar sesión para editar los datos de Conocimiento Común.
Para más ayuda, consulta la página de ayuda de Conocimiento Común.
Título canónico
Información del conocimiento común inglés. Edita para encontrar en tu idioma.
Título original
Títulos alternativos
Fecha de publicación original
Personas/Personajes
Lugares importantes
Eventos importantes
Películas relacionadas
Premios y honores
Epígrafe
Dedicatoria
Primeras palabras
Citas
Últimas palabras
Aviso de desambigüedad
Editores
Blurbistas
Idioma original
DDC/MDS Canónico
Winner of the 2011 Jolt Excellence Award! Getting software released to users is often a painful, risky, and time-consuming process. This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-- sometimes even minutes-no matter what the size of a project or the complexity of its code base.   Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the "deployment pipeline," an automated process for managing all changes, from check-in to release. Finally, they discuss the "ecosystem" needed to support continuous delivery, from infrastructure, data and configuration management to governance.   The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes   * Automating all facets of building, integrating, testing, and deploying software * Implementing deployment pipelines at team and organizational levels * Improving collaboration between developers, testers, and operations * Developing features incrementally on large and distributed teams * Implementing an effective configuration management strategy * Automating acceptance testing, from analysis to implementation * Testing capacity and other non-functional requirements * Implementing continuous deployment and zero-downtime releases * Managing infrastructure, data, components and dependencies * Navigating risk management, compliance, and auditing   Whether you're a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever--so you can deliver value to your business rapidly and reliably.  

No se han encontrado descripciones de biblioteca.

Descripción del libro
Resumen Haiku

Enlaces rápidos

Cubiertas populares

Valoración

Promedio: (3.85)
0.5
1 1
1.5
2 2
2.5
3 6
3.5 1
4 11
4.5
5 9

¿Este eres tú?

Conviértete en un Autor de LibraryThing.

 

Acerca de | Contactar | LibraryThing.com | Privacidad/Condiciones | Ayuda/Preguntas frecuentes | Blog | Tienda | APIs | TinyCat | Bibliotecas de Figuras Notables | Primeros Reseñadores | Conocimiento Común | 159,004,816 libros! | Barra superior: Siempre visible