GitOps, Jenkins, and Jenkins X
Are you ready for the next stage of development? JAX London speaker Tracy Miranda explains how GitOps is ready to save the day in the event of complete system failure.
Cloud development led us first to DevOps. Some are already declaring DevOps as the new legacy and that a new paradigm is needed to meet the needs of cloud-native development. Enter GitOps. Initially proposed by Alexis Richardson, GitOps offers to be the new community of practice where we push code not containers and perform operations by pull request.
The most valuable concept that falls under the GitOps umbrella is the Mean Time to Recovery (MTTR). Simply put: If your system failed completely, how long would you take to get it up and running from scratch? Using GitOps, Alexis’ team can recover in five minutes. Five minutes. That underlines the ultimate promise of GitOps. Let’s face it; you don’t have to look hard for many systems brought down by system engineering failures. For example, there’s the recent Google Big Query outage.
The key to optimizing your MTTR is treating your ops configuration as code. No more hand-coded magic setup that was once done by somebody who may or may not be at hand when the system fails.
JAX London “DevOps & Continuous Delivery” track
Interested in learning more about GitOps? Tracy Miranda will be at JAX London this October. Her talk, “Gitops, Jenkins & Jenkins X” is a part of the DevOps and Continuous Delivery track. This track is all about today’s technology challenges, as well as the dos and don’ts and ups and downs of modern software architecture. Join us at JAX London!
For Jenkins users, this is achievable using the configuration-as-code (CasC) plugin. This is a relatively new plugin that is currently under very active development. It lets you configure your Jenkins setup declaratively using Yaml. This provides configuration for Jenkins initial setup to give you a fully working master. It includes configuration for pipeline jobs as well as Jenkins plugins since CasC supports most plugins out of the box.
GitOps and mean-time-to-recovery become even more crucial when it comes to running scalable, high availability systems. Typically, these systems will be running in a cluster or perhaps in the cloud. Many are standardizing on using Kubernetes. Enter Jenkins X. Jenkins X rethinks CI/CD in the cloud with a focus on making development teams productive through automation, tooling and best practices. Naturally, these best practices focus on GitOps, using git as a source of truth and built-in automation to ensure your mean-time-to-recovery is a priority from the start.
Join me at JAX London to see GitOps in action as we aim to get your mean-time-to-recovery optimized with Jenkins and Jenkins X.