Daniel Fridkin · Home
עברית
עברית
Back to projects

Platform Engineering / CI/CD

GitLab Migration and CI Platform

Led the initial migration from Bitbucket Data Center and Jenkins toward GitLab CI/CD for 300+ projects, using reusable CI components, standardized templates, and Go-based migration tooling.

Production work

Delivery workflow

One platform for source and delivery

A simplified view of the migration and delivery scope: consolidate source and CI, standardize pipelines, then connect GitOps delivery.

  1. Migrate the estate

    Move repositories and CI workflows with automation.

    • Bitbucket Data Center
    • Jenkins
    • Go

  2. Standardize delivery

    Self-hosted GitLab with reusable CI components and templates.

    • GitLab
    • GitLab CI

  3. Adopt GitOps

    Controlled Kubernetes delivery and end-to-end pipelines.

    • Argo CD
    • Kubernetes

The challenge

The organization needed to move away from Bitbucket Data Center because of Atlassian's product direction and consolidate source control, CI/CD, automation, and DevOps workflows in one platform.

The approach

Drove the initial migration work into self-hosted GitLab, then hired, onboarded, and led the DevOps/platform team while creating reusable CI components, standardized pipeline patterns, Argo CD/GitOps workflows, and Go-based automation tooling for a single platform that could hold repositories, pipelines, and delivery workflows together.

My role

Founded the DevOps department as the initial solo owner with developer support, led the initial migration automation, hired and led the team for the following year, introduced Argo CD/GitOps, supported CI/CD standardization, and shaped GitLab as the central DevOps platform through templates, reusable components, and developer-focused workflows.

Engineering decisions

Consolidate the developer workflow

Bring source control, CI/CD and delivery automation into GitLab as a central DevOps platform.

Reuse shared CI components

Standardize templates and components across the 300+ project estate to reduce recurring manual pipeline maintenance.

Scope & delivery

  • Migration from Bitbucket Data Center and Jenkins into self-hosted GitLab.
  • Consolidation of source control, CI/CD, automation, and delivery workflows into one DevOps platform.
  • Reusable GitLab CI components and delivery templates.
  • Argo CD/GitOps adoption for Kubernetes delivery.
  • Full E2E pipelines for microfrontend development and production rollout.
  • Go-based tooling for repository and CI migration tasks.
  • Standardized workflows that reduce manual pipeline maintenance.
Next projectKubernetes and GitOps Infrastructure