DevOps World | Jenkins World 2019 San Francisco

"More and more teams are deploying cloud native applications on Kubernetes, placing new demands on engineers who want to deploy and test easily during their development workflow. Traditional CI/CD systems haven't been designed for cloud native environments and need to evolve. Jenkins X is a cloud native CI/CD platform that has done just that, integrating tools in the Kubernetes ecosystem for an opinionated open source solution. In this talk, we'll explain the CI/CD challenges in a cloud native landscape, and show how Jenkins X rises to them by leveraging open source cloud native technologies like Tekton. We will describe how the Jenkins X project has evolved on it's own cloud native journey and the amazing benefits we are gaining by using the cloud well. People who attend will leave with a better understanding of the awesome new technologies, architecture and benefits which are transforming the way we build, release, deploy and run our software."

"Blue/Green deployments can reduce downtime and risk when pushing applications to production. The best practice where one production environment serves a live application, and another an area to deploy and test before replacing it, forms the basis of a conversation about extending the practice to the pipeline itself. When DevSecOps pipelines fail, continuous delivery grinds to a halt. Often the break is due to teams making changes to increase flow and reduce waste or the integration of a new tool. Security tools are notorious for being slow and should be tested without any adverse effects to the delivery process. With a Blue/Green pipeline approach powered with automation, teams can experiment on a parallel pipeline without impacting the needs of the business Join DJ as he introduces the technique of operating with Blue/Green pipelines, how to use Infrastructure as code to create them, experimentation with security toolsets and the architectural concerns that need to be considered when utilizing this approach to reduce the risk of pipeline breaks."

Want to know how Jenkins builds Jenkins? Catch this session to see the real-life implementation of Jenkins' development (at ci.jenkins.io) and delivery infrastructure in the cloud as it evolved from a mix of platforms to multi-platform VMs, containers and Kubernetes on Microsoft Azure. Expect a frank discussion of issues that were encountered along the way, how the architecture has evolved and what's on the roadmap. We'll share important tips and tricks for implementing your own Jenkins infrastructure on any cloud, based on Jenkins' own implementation experience.

In this case study we present the multi-cloud approach of deploying the Adobe Sign service to multiple geographies using both Amazon Web Services (AWS) and Microsoft Azure. We will discuss driving forces behind multi-cloud adoption, the pros and cons of the approach and cover strategies developed to achieve a "push button" deployment to both clouds using in-house and third-party tools.

"Shared libraries enable Jenkins administrators and developers to make standard functionality available for use in pipeline jobs. When done properly, the libraries simplify Jenkins files, ensure compliance steps are performed, and allow easy customization of jobs. When done wrong they become a never-ending nightmare of complicated code updates, breaking changes, untold numbers of support tickets, and unhappy users. At Liberty Mutual we charged headlong into pipelines with no hesitation...or planning. After two years of development we were left with over 20000 lines of incomprehensible code—it was difficult to update and impossible to unit test. We’ve refactored many methods, but with so much untestable code, this effort was fraught with danger. The decision was made to scrap the entire codebase and start from scratch.

In this session we will dive into the mistakes that were made and how to avoid them. We will cover the basics of planning the code structure, modular methods, and how to test. We will also discuss the inner source model Liberty uses to extend pipeline functionality by allowing users to contribute code."