Welcome!

@DevOpsSummit Authors: Liz McMillan, Pat Romanski, Elizabeth White, Yeshim Deniz, Zakia Bouachraoui

Related Topics: @DevOpsSummit, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

Incident Management and Continuous Integration | @DevOpsSummit #APM #DevOps #ContinuousIntegration

Often mentioned in the same breath as continuous integration is continuous deployment

Incident Management and Continuous Integration, a Partnership for Success
By Zachary Flower

As a developer, I’m a huge fan of continuous integration. For the uninitiated, continuous integration is a software engineering practice in which code changes are tested as soon as they are committed. This enables early problem detection. It also provides immediate feedback on code quality, allowing for issues to be identified and fixed immediately.

Often mentioned in the same breath as continuous integration is continuous deployment. Continuous deployment is an extension of continuous integration in that, as soon as the unit tests pass, the code is immediately released to production. By continuously integrating and deploying code changes, developers can reduce risk and quickly adapt the product to the business’ needs. This process, while incredibly valuable to both developers and users, does have some room for improvement.

As in a production environment, integrating your team’s incident management process into your continuous integration workflow is an excellent way to improve communication and transparency around failed builds. Sending the details of failed builds to an incident management platform such as PagerDuty can provide a number of benefits that go way beyond the standard notifications many continuous integration tools provide.

Premortems
One of the biggest benefits that incident management techniques can bring to continuous integration is the concept of the “premortem.” A postmortem, in project management terms, is the process of examining and identifying the elements of a project launch that were successful or unsuccessful. While this process is often done at the successful completion of a project, in terms of incident management, it involves understanding and communicating the root cause of a critical failure.

By integrating this process into the continuous integration workflow, you perform a premortem. With a premortem you are looking for problems in advance. What problem may potentially occur that may disrupt service and trigger an incident. Testing for failures and potential service disrupting incidents during the the continuous integration phase allows teams to evaluate potential threats and make changes before things even reach the end user.

Training
Training junior developers is an important part of running a successful development team. Unfortunately, successful incident management in a production environment can be fast-paced and stressful. While the team can run a postmortem the morning after a late-night issue occurs and is mitigated, the information that can be conveyed during those postmortems might not be as easy to consume by the more novice members of the team. By pushing issues raised in the continuous integration workflow directly into your incident management process, you can provide junior developers with an opportunity to learn more about the process in a significantly less stressful environment.

Growth
I’m a big fan of code reviews. I have always found them to be an important tool for the professional growth of every member of the development team, no matter what level of experience they have. By pairing an incident management platform with the continuous integration workflow, you can use the details of failed builds as a supplement to the code review process to identify specific areas of the code that should be discussed in more detail. This is an excellent opportunity to not only improve the code quality, but also keep the importance of the test suite at the top of the team’s mind.

Incident management is often thought of as a reactive process, but by incorporating a continuous integration toolset and mindset, you can turn it into a proactive one. Responding to and mitigating incidents before they actually happen will allow you and your team to stay two steps ahead, which will serve to reduce code debt, and improve the overall stability and reliability of your product.

The post Incident Management and Continuous Integration, a Partnership for Success appeared first on PagerDuty.

More Stories By PagerDuty Blog

PagerDuty’s operations performance platform helps companies increase reliability. By connecting people, systems and data in a single view, PagerDuty delivers visibility and actionable intelligence across global operations for effective incident resolution management. PagerDuty has over 100 platform partners, and is trusted by Fortune 500 companies and startups alike, including Microsoft, National Instruments, Electronic Arts, Adobe, Rackspace, Etsy, Square and Github.

@DevOpsSummit Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.
In an era of historic innovation fueled by unprecedented access to data and technology, the low cost and risk of entering new markets has leveled the playing field for business. Today, any ambitious innovator can easily introduce a new application or product that can reinvent business models and transform the client experience. In their Day 2 Keynote at 19th Cloud Expo, Mercer Rowe, IBM Vice President of Strategic Alliances, and Raejeanne Skillern, Intel Vice President of Data Center Group and GM, discussed how clients in this new era of innovation can apply data, technology, plus human ingenuity to springboard to advance new business value and opportunities.
DXWorldEXPO LLC announced today that "IoT Now" was named media sponsor of CloudEXPO | DXWorldEXPO 2018 New York, which will take place on November 11-13, 2018 in New York City, NY. IoT Now explores the evolving opportunities and challenges facing CSPs, and it passes on some lessons learned from those who have taken the first steps in next-gen IoT services.
The current age of digital transformation means that IT organizations must adapt their toolset to cover all digital experiences, beyond just the end users’. Today’s businesses can no longer focus solely on the digital interactions they manage with employees or customers; they must now contend with non-traditional factors. Whether it's the power of brand to make or break a company, the need to monitor across all locations 24/7, or the ability to proactively resolve issues, companies must adapt to the new world.