GitOps for the people

What if your non-technical stakeholders could approve production deployments directly from a Jira ticket? Learn a new GitOps pattern that makes it possible.

#1about 3 minutes

Introducing MoneyBank's enterprise engineering challenges

A highly regulated fintech enterprise with 200 engineers struggled with unclear responsibilities and strict compliance requirements.

#2about 3 minutes

Identifying manual processes and proposing automated solutions

Manual QA, environment configuration drift, and compliance by committee were addressed by introducing automated testing, Kubernetes, and GitOps.

#3about 2 minutes

Understanding the fundamental principles of GitOps

GitOps uses a Git repository as the single source of truth to declaratively manage the state of an application's infrastructure.

#4about 4 minutes

Analyzing the legacy manual deployment process

The original workflow involved long-lived release branches, a manual release manager role, and multiple handoffs between teams for deployment.

#5about 3 minutes

Implementing a new CI/CD architecture with GitOps

The new architecture used separate app and configuration repositories, with Jenkins and Argo CD automating deployments up to a manual pull request approval for production.

#6about 4 minutes

Introducing ReleaseOps to bridge the technical gap

ReleaseOps was created to involve non-technical stakeholders by using Jira ticket statuses to trigger automated CI/CD events, replacing pull request approvals.

#7about 2 minutes

Architecting the complete ReleaseOps workflow

The final architecture integrated Jira, Bitbucket, Tecton pipelines, and Argo CD to create a fully automated, ticket-driven release process.

#8about 3 minutes

Key principles for building an internal developer platform

Building a successful internal developer platform requires treating it like a product with a focus on user experience, self-service, and optional adoption.

#9about 4 minutes

Answering questions on ReleaseOps and process philosophy

The discussion clarifies that testing happens on deployed environments and emphasizes focusing on processes that unite technical and non-technical teams over rigid methodologies.