A highly regulated fintech enterprise with 200 engineers struggled with unclear responsibilities and strict compliance requirements.
Manual QA, environment configuration drift, and compliance by committee were addressed by introducing automated testing, Kubernetes, and GitOps.
GitOps uses a Git repository as the single source of truth to declaratively manage the state of an application's infrastructure.
The original workflow involved long-lived release branches, a manual release manager role, and multiple handoffs between teams for deployment.
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.
ReleaseOps was created to involve non-technical stakeholders by using Jira ticket statuses to trigger automated CI/CD events, replacing pull request approvals.
The final architecture integrated Jira, Bitbucket, Tecton pipelines, and Argo CD to create a fully automated, ticket-driven release process.
Building a successful internal developer platform requires treating it like a product with a focus on user experience, self-service, and optional adoption.
The discussion clarifies that testing happens on deployed environments and emphasizes focusing on processes that unite technical and non-technical teams over rigid methodologies.
28:45Lian Li
17:31Axel Barbier
31:02Hauke Brammer
36:09Chad Carlson
47:42Roberth Strand
50:02Liviu Costea
25:24Florian Trieloff
58:44Davide Imola
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
smartclip Europe GmbH
Hamburg, Germany
iits-consulting GmbH
München, Germany
SYSKRON GmbH
Regensburg, Germany
CONTIAMO GMBH
Berlin, Germany
Atruvia AG
Berlin, Germany
