Skip to content

GitOps Migration Planning

Purpose: Active migration work from Jenkins X to GitHub Actions + ArgoCD

Important: This folder is temporary - it will be deleted when the migration completes. A summary will be preserved in /architecture/migration-summary.md.

Migration Documents

Active Sprint Work

  • sprint-current.md - Current sprint plan
  • Story 2.4: Promotion PR Automation (2-3 hrs)
  • Story 3.4: ApplicationSet for PR Previews (2-3 hrs)
  • Total: 4-6 hours with AI assistance
  • Next: Complete these stories before provisioning GKE cluster

Status Tracking

  • status.md - Current migration status
  • Overall Progress: 46% complete (12/26 stories)
  • Verified against actual code (not documentation)
  • Last updated: 2025-11-04
  • Updated as stories complete

Full Backlog

  • backlog.md - Complete migration backlog
  • All 26 user stories across 5 epics
  • Story points and acceptance criteria
  • Dependencies and blockers identified
  • Epic 1: ✅ Complete (Monorepo Foundation)
  • Epic 2: 🔄 In Progress (CI/CD Automation)
  • Epic 3: 🔄 In Progress (GitOps Infrastructure)
  • Epic 4: ⏳ Blocked (ArgoCD Deployment - needs K8s cluster)
  • Epic 5: ⏳ Planned (Production Migration)

Quick Status

✅ Completed (12/26 stories - 46%)

  • Monorepo refactoring
  • GitVersion configuration (ContinuousDeployment mode)
  • Docker builds in CI/CD pipeline
  • GitOps repository setup (cluster-gitops)
  • ArgoCD Application YAMLs
  • Environment values files

🚀 This Sprint (4-6 hrs)

  • Story 2.4: Promotion PR Automation
  • Story 3.4: ApplicationSet for PR Previews

⏳ Blocked (Needs K8s Cluster)

  • ArgoCD installation and configuration
  • Application deployment and testing
  • Production migration (14 stories)

Permanent Documentation (Survives Migration)

  • cluster-gitops - GitOps configuration repository with ArgoCD manifests

Timeline

  • Sprint Length: 1 week
  • Target: ASAP with comfortable quick cutover
  • Approach: Complete Stories 2.4 and 3.4, then provision cluster
  • Team Preference: Nuri working solo with review checkpoints

When Migration Completes

  1. Create summary: Add lessons learned to /docs/architecture/migration-summary.md
  2. Preserve decisions: All ADRs in /docs/decisions/ are permanent records
  3. Delete this folder: Entire docs/planning/migration/ folder will be removed
  4. Git history: All planning docs preserved in git history if needed

Notes

  • Progress verification: Always check actual code, not just documentation
  • AI assistance: Story points assume 60-70% time savings with AI pair programming
  • Test environment: This is a TEST repo - production approach may differ
  • Updates: Status and sprint files updated as work progresses