GitHub EMU Implementation, BitBucket Server to GitHub Migration and Jenkins Pipeline to GitHub Action Migration – XPT Software

GitHub EMU Implementation, BitBucket Server to GitHub Migration and Jenkins Pipeline to GitHub Action Migration

GitHub EMU Implementation, BitBucket Server to GitHub Migration and Jenkins Pipeline to GitHub Action Migration

GitHub EMU Implementation

BitBucket Server to GitHub Migration and Jenkins Pipeline to GitHub Action Migration

Summary: Migration of BitBucket server repositories into GitHub

Tech Stack: bbs-exporter, ECI, Python Scripting

Requirements	Solution	Results
Decommission legacy Jenkins pipelines and migrate 1200+ pipelines to GitHub Actions Standardize pipelines across diverse tech stacks (Java, Go, Node.js, Python) Overcome GitHub’s workflow_dispatch input limits (10 parameters) Enable scalable, cost-efficient runners via ARC on Kubernetes Ensure backward compatibility with legacy workloads (older GLIBC versions)	Migrated 1200+ Jenkins pipelines into modular reusable workflows in GitHub Actions Built a dynamic reusable workflow that detects tech stack at runtime Introduced JSON-based metadata configs in each repo → bypass GitHub input limitations Centralized workflows: reusable-workflows (governed core workflows) main-workflows (service triggers) Built 16 ARC runner pools (Ubuntu 22.04 + Ubuntu 16.04 for legacy compatibility)	20% faster build times compared to Jenkins Eliminated Jenkins infra overhead (masters/agents) → reduced costs Improved developer productivity with GitHub-native CI/CD Standardized pipelines across multiple teams & stacks Strengthened governance with centralized workflows and security policies Achieved backward compatibility for legacy workloads via custom ARC runners

Click outside to hide the comparison bar

Compare