Presentation: CI/CD: Lessons from LinkedIn and Mockito

Since many years my passion is developer productivity at scale. I started this back in 2007, when I attempted to change how Java engineers write unit tests with mocks (Mockito framework). Today I help with engineering productivity at LinkedIn in two ways.

Firstly, my team provides development tools and workflows to 3000 LinkedIn engineers. We manage code review, continuous integration, commit-to-publish pipeline, IDE integrations, dependency management and many more. We maintain cohesive engineering culture because every team is using standard development workflow. I tech lead the efforts of building great tools for developers.

Secondly, I am deeply involved in training and developer education programs. I often design and develop training because it really helps boosting productivity in engineering teams.

In the open source and in the enterprise continuous delivery is not yet adopted as widely as it should given how it helps with productivity. I hope engineering teams will experiment more with continuous delivery and try to push themselves to go into that model.

Developers and architects who want help teams increase their productivity by shipping to production frequently and automatically.

Learn about the challenges and advantages of adopting continuous delivery at scale. Get excited to reduce manual steps from commit-to-production pipeline. Get practical suggestions, too! Continuous delivery is hard but you really want to push great features to your customers faster.

There are challenges at LinkedIn that keep me excited and very busy. Reducing commit-to-publish time for every engineering team is a big one. It’s because shipping code faster is probably the most tangible way of increasing developer productivity.

Another challenge is dependency management at scale. How to manage version upgrades, dependency conflicts, large scale changes that require updates to thousands of codebases? In the Open Source I would love to push the community towards continuous delivery model for software libraries. Mockito framework paved the way for this model. Me and other enthusiasts from Mockito community work on a new release automation framework called “Shipkit” - a toolkit for shipping it.

I still contribute to Mockito regularly, and I focus on strategic API extensions that help other frameworks like Spring Boot or Powermock to cleanly integrate with Mockito. My goal is to ensure thoughtful evolution of Mockito API so that it remains the best mocking framework for Java.