continuous integration

The dream of any product owner is fully customizable production software without the expense of the hardware it rests upon. While not completely free of infrastructure, serverless infrastructure significantly reduces overhead costs by abstracting away physical hosting, physical security, server maintenance, and OS patching. Here's what you need to know to decide if serverless infrastructure is right for you.

It’s usually easy and inexpensive to set up a continuous integration environment for either an agile or a waterfall project. Perhaps the most obvious benefit of CI is the elimination of the integration phase that existed in traditional waterfall projects, where we typically slip the worst on deadlines. But there are many other benefits to continuous integration that you may not have considered.

Peer-to-peer Discussion: How Do I Make CD Work in My Environment? Building a successful continuous delivery pipeline is very context specific. Large organizations with legacy code, existing physical environments, regulatory constraints, large monolithic applications, or stove piped organizations often struggle to find a continuous delivery approach that will work for them successfully. If this sounds familiar, this session is for you. Join facilitator Lee Eason as conference participant’s work together to identify and solve difficult continuous delivery challenges. Learn how other participants and speakers have dealt with the issues you have within their own companies and how you can apply their lessons learned. Share your successes and help others solve their DevOps problems. Expand upon questions you’ve asked during others sessions so you leave the conference with even more ideas for addressing your CD challenges.

Are you a developer who wants to easily manage and customize continuous integration and delivery? Do you work in a team environment where everyone collaborates and depends on CI for automation and delivery of clean code to production? In this session, Amit Mishra will share a case study of how Credit Karma evolved from a single, standalone CI instance to a self-service, Dockerized CI infrastructure combined with bots, webhooks, and GitHub APIs. He will cover GitHub's features and powerful APIs that were most valuable in this process, and how using GitHub freed up time previously spent on maintaining the underlying infrastructure. Credit Karma’s development teams are now empowered to spin up their own CI instances and add custom checks as part of their CI process to ensure quality code. This allows teams to focus simply on developing and delivering services.