Rabu, 25 Agustus 2010

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1),

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), By Juni Mukherjee. Eventually, you will certainly find a brand-new adventure and also knowledge by investing even more money. But when? Do you assume that you should obtain those all requirements when having significantly money? Why don't you attempt to get something easy at very first? That's something that will lead you to know more about the world, experience, some locations, past history, amusement, and a lot more? It is your very own time to proceed reading routine. Among guides you can enjoy now is Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), By Juni Mukherjee right here.

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee



Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Download PDF Ebook Online Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

I have worked in Continuous Delivery projects for yet-to-be-famous tech startups and with well-established companies like Apple, Yahoo!, GoPro, ThoughtWorks, Walmart.com and PricewaterhouseCoopers Ltd. I share my experience of releasing software from a source code control repository to Production, and how the manual processes can be fully automated with good design and smart decisions. In this book, I zoom in on the choking points, so that my readers can accelerate through their own design and implementations. This is how I have structured the book: Chapter 1: Introduction Eases my readers into understanding and appreciating a Continuous Delivery Pipeline, removes confusion between Continuous Integration and Continuous Delivery, gives a brief introduction about me and who I am grateful to. Chapter 2: Pipeline Architecture and Design Establishes basic definitions, explains how CD’s success depends on the Product Architecture, designs the CD Pipeline Architecture, designs the various stages of the Pipeline from Git to Production, talks about Pipeline Visualization and the emphasizes the importance of managing Pipeline artifacts. Chapter 3: Continuous Testing - Choking Points Discusses the types of tests that need to be done in the Pipeline, the tests that are not types by themselves but just concepts, a three-tier Test Framework Design that improves maintainability, Test Data Strategy and Data Generation techniques, the downside of traditional Test Case Repositories and Test Reporting as part of Continuous Delivery. Chapter 4: Continuous Deployment - Choking Points Discusses dependency management, pre-deploy hooks and post-deploy hooks, anxiety about deployment to Production and Immutable Infrastructure. Chapter 5: Code Promotion - One Stage At A Time Discusses institution of software gates that allow/disallow the flow of code from one stage of the Pipeline to the next, all the way to Production through a Continuous Delivery environment. Chapter 6: Release and Change Management Discusses Feature Branches, respecting the Mainline, Feature Toggles, Release Toggles, Business Toggles, Rollback Strategy, A/B tests and Canary Releases. Chapter 7: The Magnificent Seven Discusses the seven areas, which have tripped Continuous Delivery teams in the past, namely Cloud, Big Data, Data Science, Databases, Mobile, People and Budget. Chapter 8: Continuous Delivery Analytics Detailed discussion on success metrics, pre-production signals, post-production signals, Stability Index and its relationship to signals and designing Continuous Delivery dashboards that measure ROI. Chapter 9: CD-as-a-Service Talks about designing a CD Minimum Viable Product, discusses offering the CD platform as a PaaS such that teams can sign a Pipeline Contract and hop on, discusses the structure of the Pipeline Contract and how to make CD-as-a-Service secure. Chapter 10: Continuous Delivery in an Agile Framework Discusses the importance of having a single, prioritized Product Backlog, Sprint Backlog, Feature Team, Product Owner and their roles in CD, Scrum Master, Tech Lead, DoD - Definition Of Done, Impediment Backlog and how code is the new documentation, unless it's spaghetti. Chapter 11: The Beginning Discusses CD patterns and anti-patterns and illustrates how Continuous Delivery can be applied to industries other than software. Chapter 12: Resources Places where you can find great information. Overall, this book discusses Continuous Delivery Pipeline design and implementation aspects and provides thought leadership for teams building a Continuous Delivery Pipeline. Tools is an evolving area and this book focuses on the big picture, instead of making strong recommendations on any tool. While I mention a lot of different tools that I have used in the industry, my readers are encouraged to do their own research.

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

  • Amazon Sales Rank: #489819 in Books
  • Published on: 2015-05-29
  • Original language: English
  • Number of items: 1
  • Dimensions: 8.00" h x .39" w x 5.00" l, .38 pounds
  • Binding: Paperback
  • 156 pages
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

About the Author LinkedIn: https://www.linkedin.com/in/junim Juni has worked in Continuous Delivery projects for yet-to-be-famous tech startups and with well-established companies like Apple, Yahoo!, GoPro, ThoughtWorks, Walmart.com and PricewaterhouseCoopers Ltd. She shares her experience of releasing software from a source code repository to Production, and how the manual processes can be automated with good design and smart decisions. Continuous Delivery is not a discipline on it’s own and the science behind it is rarely taught in schools. This book helps folks build and strengthen their Continuous Delivery Pipelines.


Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Where to Download Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Most helpful customer reviews

2 of 2 people found the following review helpful. Insightful, engaging and informative journey to building or enhacing CI/CD pipelines. By Amazon Customer The book takes us into the journey of building a resilient CI/CD pipeline sending a strong message about keeping both the company applications and the infrastructure they run on as versioned controlled source code. It covers the challenges at each phase, the strategies to prevent a "choke" and in some sections the tools needed to enhance or build that specific part of the pipeline. I like that the author also provides strategies on how to deal with the "How do we keep the whole team engaged, informed and heading on the same direction?" challenge by covering a strategy to keeping a prioritized product and sprint backlog.I particularly found useful chapter 8 - CD Analytics and chapter 9 - CD as a Service, the latter being my favorite as well as the section on the "Internet of Things" towards the end of the book. Building CI/CD as a service is a huge project especially when servicing big teams in distributed geographical locations. Juni goes in detail describing how to build CI/CD as a service and what it will take to make this happen addressing issues with authentication/authorization, auditing and proving sample metrics to trend the health of the pipeline.In future versions of the book, I would love to see screenshots of actual dashboards in action covering the key metrics mentioned on the chapter 8, this is taking into account the the author's advice of not becoming a "Metrics" person but rather use the trended information to gain better understanding of the "people behavior and product stability." Also, adding pipeline pattern diagrams would make the story far easier to visualize.Overall, lots of good information covered on an easy to follow 147 page journey plus some additional resources. I recommend reading this book to Software, DevOps Engineers or any one interested in getting a different perspective on what it takes to build a CI/CD pipeline and building it as a service to the different Engineering teams within a given organization.

2 of 2 people found the following review helpful. Accessible and useful. By Brent Barton This book was clearly written by a practitioner who has gone through the journey of moving to Continuous Delivery (CD) multiple times. Juni gives technical recipes and examples that are actionable and understandable by both leaders and implementers. I particularly appreciate the business considerations that are embedded in this book, from budget to metrics to pipeline contracts. As organizations become “tech enabled” this book reveals modern capabilities that are fast becoming differentiators or even table stakes that require investment for - well, forever.In the book, Juni says, “Continuous Delivery is the norm in most workplaces.” How I wish that were true! It should be the norm and eventually it will be. Juni has been fortunate enough to create this for many places.I am making a list of leaders I am going to hand this book to. This is also a great candidate for a book review in organizations that want to investigate CD. For the person who wants to take on the challenge of Continuous Delivery, you have a guidebook for determining your Stability Index, discussing “testing_types” for different stages, helpful references to plug-ins and why Juni found value from them, to name a few nuggets. If I were in a high-compliance environment, I would use Juni’s book as a guide for discussing ways to break the build for violations in an automated way, giving me competitive advantage to manual auditing methods.I have two minor negatives about this book: Git is referenced often as if it is the only choice of repository. This seemed an oversight because Juni clearly stated the tools are ever-changing and often gave several options. Lastly, there are a few grammatical issues and misused colloquialisms (e.g. used “thumb rule” instead of “rule of thumb”). That said, they did not diminish my perceived value of this book.

2 of 2 people found the following review helpful. Really Helpful By Jerry Murry There are several things I really like about this book. The two that stuck out most for me:First off, Continuous Delivery is a big topic and many people initially feel overwhelmed when they attempt to address it. I appreciate that the author takes great care to break each of the areas down into much more manageable concepts and patterns. For example, when we talk about Continuous Delivery we have to also talk about Continuous Testing. In the Continuous Testing chapter Juni describes simplified test types, approaches for test data, characteristics of a test framework and test reporting. In addition to breaking the domain down to a more manageable size, she also acknowledges that Continuous Delivery solutions are not one size fits all. Given this, she recommends that each organization needs to first understand themselves and use her recommendations as a starting place that will most likely need to be tweaked to meet the team’s needs.The second challenge with Continuous Delivery is that it is quickly evolving with respect to tools. The tool that is “best in class” today may not be tomorrow so the author takes great care to separate the concepts and practices of CD from the choice of technologies. This focus on “what you do” and “why you do it” rather than on the tool means that people immediately start practicing the right behaviors. Continuous Delivery is a significant change and as with all significant changes there will be bumps along the way, but when people understand what to do and why they are doing it, many of these bumps can either be minimized or eliminated altogether. Once the tools are chosen and the proofs of concept are done, the adoption is significantly accelerated because people are already doing the right things.This is a quick read and a great book to get when you would like to drive organizational change. I look forward to her next book.

See all 9 customer reviews... Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee


Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee PDF
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee iBooks
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee ePub
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee rtf
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee AZW
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee Kindle

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee
Continuous Delivery Pipeline - Where Does It Choke?: Release Quality Products Frequently And Predictably (Volume 1), by Juni Mukherjee

Tidak ada komentar:

Posting Komentar