Continuous Delivery and DevOps: A Quickstart guide
Format: PDF / Kindle (mobi) / ePub
Streamline and optimize your workflow with this fast and engaging guide to continuous delivery and DevOps. Delivering quality software every time will become a way of life.
- Real world and realistic examples of how to go about implementing continuous delivery and DevOps
- Learn how continuous delivery and DevOps work together with other agile tools.
- An honest and open guide to consistently shipping quality software quickly.
What you will learn from this book
- Determine the problems and pain points within a product delivery process
- Tools and techniques to understand the root causes of the problems and pain points within a software delivery process
- Define and measure the success of implementing Devops and continuous delivery
- Understand the human elements to continuous delivery and DevOps and how important they are
- Avoid the traps, pitfalls and hurdles you'll experience as you implement continuous delivery and DevOps
- Monitor and communicate the relative success of DevOps and continuous deliver adoption
This book is both a practical and theoretical guide detailing how to implement continuous delivery and Devops to consistently ship quality software quickly.
Who this book is written for
Whether you are a freelance software developer, a system administrator working within a corporate business, an IT project manager or a CTO in a startup you will have a common problem; regularly shipping quality software is painful. It needn't be. This book is for anyone who wants to understand how to ship quality software regularly without the pain.
For a while now, there has been a buzz around the IT industry regarding continuous delivery and DevOps. This book will provide you with some background information into these two new kids on the block and how they can help you to optimize, streamline and improve the way you work and ultimately how you ship quality software.
"Continuous Delivery and DevOps: A Quickstart guide" will provide you with a clear and concise insight into what continuous delivery and DevOps are all about, how to go about preparing for and implementing them and what quantifiable business value they bring. Included within are some tricks and trips based upon real world experiences which may help you reduce the time and effort needed if you were to go it alone.
In this book, you will be taken through a journey of discovery starting with real world successes, how you should prepare, plan for and implement CD and DevOps and what the pitfalls are along the way.
We will start looking at the evolution of a typical software house from fledgling start-up through the growing pains that comes with global success to a best of both worlds. We'll delve into the many aspects of what they did to complete this evolution covering topics such as how they realized there was a problem to solve, how they set about preparing for and implementing continuous delivery and DevOps and what tools, techniques and approaches they used along the way – some technical and some not so. If you work within an organization that delivers software, you will be able to plot where you are on the evolutionary scale, understand where you need to do to be more effective, cherry pick the tools, techniques and approaches that work for you and realize the best of both worlds.
"Continuous Delivery and DevOps: A Quickstart guide" will provide you with the background and information you need to realize the benefits within your own business
then becomes ingrained and others will use it day to day, which means conversations will be consistent and there is much less risk of misinterpretation and confusion. You now have a goal, a vision, a high level backlog, a standard way of communicating, and you're ready to roll (almost). The execution of the plan is not something to be taken lightly. Whether you are a small software shop or a large corporate, you should treat the adoption and implementation of CD and DevOps with as much gravitas
(or better still as part of the team), you should also look into getting simple things together, such as a logo or some freebies (such as badges, mugs, mouse mats, and so on), to hand out. This may seem a little superfluous but as with any PR you will want to ensure you get the message across and have it imbedded into the environment and peoples' psyche. Up until this point, I may have painted things in a somewhat rosy glow. Adopting CD is no picnic. There's quite a big hill to climb for all
personas (Stan the manager, Devina the developer, and Oscar the ops guy) you were introduced to in Chapter 1, Evolution of a Software House. It should be noted that I am by no means an expert in the human sciences, nor do I have a PhD in psychology. What follows are learnings through observation, experience, and collaboration with experts in these fields. Let's start by clarifying why culture is so important to CD and DevOps. All roads lead to culture Some people might think that CD
data that is of no value to you at all. I'll cover some examples in Appendix D, Vital Measurements Expanded, but simply put, this approach falls into two categories: Incorporate a health-check function within your software APIs; this will provide low-level metrics data when called periodically by a central data collection solution Extend your software platform to push low-level metrics data to a central data collection solution periodically You will, of course, need something to act as the
the platform. Although this is a viable approach, it does add something to the code base, which can, over time, become a massive headache—complexity. It also adds complexity to the overall testing—especially if you start to chain the feature flags together (for example, feature C is on if feature A is on, but feature B is off). Having adopted CD and DevOps, you will be shipping code with ease, and you'll have the Dev and Ops team working as one. Therefore, it would be far simpler to consider