Persistent Systems Ltd./ Optum, United Health Group/ February 2025 - Present

DT&P and RT Migration to GitHub

Successfully migrated 300+ repositories from GitLab to GitHub and established robust Continuous Deployment (CD) pipelines using GitHub Actions. Migrate GitLab pipelines to GitHub Actions for Real Time, DT&P and Payer Connectivity Services (PCS)-Batch. As part of CI/CD migration, Real Time and DT&P repositories and pipelines to be migrated in milestones from GitLab CI and Octopus Deploy to GitHub Actions. As part of the CI/CD implementation, Jenkins pipelines for Payer Connectivity Services (PCS)-Batch repositories are to be built by transitioning the source code platform from GitLab to GitHub. The objective is to standardize and streamline CI/CD workflows across all repository types, consolidating them on GitHub Actions where applicable, while continuing with Jenkins for PCS-Batch.

GitHub ActionsAWS Secrets ManagerJenkinsGitLabOctopus DeployArtifactory
300+
Repositories Migrated
Migrated from GitLab CI and Octopus Deploy to GitHub Actions
3
Platforms Unified
GitLab, Octopus Deploy, and Jenkins consolidated onto GitHub
99.9%
Pipeline Uptime
Validated through shadow testing on Optum runners
Business Challenge

Optum needed to standardize and modernize its CI/CD workflows across Real Time, DT&P, and PCS-Batch repositories while eliminating dependency on GitLab CI and Octopus Deploy. The challenge was to migrate 300+ repositories and sustain zero disruptions during a critical platform transition.

5 items

Objective

  • Migrate GitLab pipelines to GitHub Actions for Real Time, DT&P and Payer Connectivity Services (PCS)-Batch.
  • Migrate CI/CD pipelines for Real Time and DT&P repositories from GitLab CI and Octopus Deploy to GitHub Actions.
  • As part of CI/CD migration, Real Time and DT&P repositories and pipelines to be migrated in milestones from GitLab CI and Octopus Deploy to GitHub Actions.
  • As part of the CI/CD implementation, Jenkins pipelines for Payer Connectivity Services (PCS)-Batch repositories are to be built by transitioning the source code platform from GitLab to GitHub.
  • The objective is to standardize and streamline CI/CD workflows across all repository types, consolidating them on GitHub Actions where applicable, while continuing with Jenkins for PCS-Batch.
6 items

Solution

  • GitLab Pipelines: Discover and migrate build setups across projects into individual GitHub workflows.
  • DT&P Pipelines: Migrate projects and runbooks to GitHub using main and shared workflows.
  • Secrets and Variables: Use AWS Secrets Manager to manage and retrieve pipeline secrets.
  • Target Deployment with Remote Execution: Dynamically generate target list and deploy via GitHub Actions.
  • Dynamic Variable Substitution: Apply GitHub Actions to replicate Octopus variable substitution feature.
  • Test and Documentation: Validate workflows on Optum runners and complete documentation and knowledge transfer.
4 items

Impact & Benefits

  • Lower Cost: Leveraged GitHub Actions free tier with Enterprise license and self-hosted runners.
  • Pipeline-as-Code: Embedded pipelines directly into application source code for better versioning.
  • Centralized Access Control: Consolidated policies in GitHub, removing the need for fragmented maintenance.
  • Agentless Deployment: Eliminated the need to install agents on target servers.
2 items

Challenges & Mitigations

  • Migration Errors: Mitigated by utilizing shadow testing to validate workflows safely.
  • Secrets Exposure: Secured sensitive data using GitHub Encrypted Secrets and AWS Secrets Manager.
6 items

My Roles & Responsibilities

  • Led end-to-end project planning and execution for the migration of DT&P, RealTime, and PCS CI/CD pipelines from GitLab CI and Octopus Deploy to GitHub Actions.
  • Coordinated across development, DevOps, platform, security, and business teams to align scope, timelines, dependencies, and migration priorities.
  • Established governance cadence, tracked milestones, managed risks and dependencies, and ensured timely resolution of project roadblocks.
  • Drove stakeholder communication through regular status reporting, executive updates, migration readiness assessments, and release planning discussions.
  • Oversaw validation, shadow testing, documentation, and knowledge transfer activities to ensure a smooth and low-risk transition to GitHub Actions.
  • Ensured successful delivery by maintaining focus on schedule adherence, quality, security compliance, standardization of CI/CD practices, and stakeholder satisfaction.