Legacy Pipeline to Cloud-Native CI/CD Migration Blueprint

Role: Principal Platform Engineer specializing in enterprise continuous delivery and build infrastructure modernization.

Context

• Existing build infrastructure and tooling: {{legacy_toolchain}}
• Target modern CI/CD solution: {{target_ci_platform}}
• Primary performance and operational bottlenecks: {{build_bottlenecks}}
• Production and staging deployment environments: {{deployment_targets}}
• Maximum acceptable commit-to-production lead time: {{max_lead_time_target}}
• Mandated quality and security gates: {{security_gates}}

Task

Generate an actionable, phased migration plan to transition engineering teams from {{legacy_toolchain}} to {{target_ci_platform}}, reducing pipeline lead times toward {{max_lead_time_target}} while preserving {{security_gates}} across all {{deployment_targets}}.

Method

1. Analyze current build failure modes and bottlenecks reported in {{build_bottlenecks}} to isolate legacy dependencies.
2. Design target runner topologies, caching layers, and parallel execution matrix within {{target_ci_platform}}.
3. Define a phased wave migration strategy (pilot services, shared libraries, core monolith, high-throughput microservices).
4. Specify dual-running protocols and automated parity testing between {{legacy_toolchain}} and {{target_ci_platform}}.
5. Standardize reusable pipeline templates enforcing {{security_gates}} and automated rollback triggers.
6. Detail deployment workflows targeting {{deployment_targets}} utilizing blue-green or rolling mechanisms.
7. Formulate a cutover schedule, fallback runbooks, and platform engineer training milestones.

Constraints

• MUST maintain continuous release capability with zero pipeline freeze exceeding 30 minutes during cutovers.
• MUST NOT leave pipeline secrets, keys, or tokens in static YAML configurations; mandate secret manager integrations.
• Every migration phase must have explicit rollback criteria and success telemetry.
• Recommendations must directly address the specific constraints of {{build_bottlenecks}}.

Output format

• Executive Summary (1 paragraph)
• Migration Architecture & Runner Topology (structured list with specifications)
• Phased Wave Implementation Schedule (4 distinct phases with deliverables, dependencies, and risks)
• Parity & Rollback Playbook (step-by-step checklist)
• Operational Telemetry & Success Metrics (KPI table: Metric, Target, Measurement Method)

Self-review

• Ensure all variables including {{target_ci_platform}} and {{security_gates}} are explicitly integrated into migration phases.
• Confirm no steps require hard downtime on active production delivery branches.
• Verify the total proposed workflow achieves the targeted lead time of {{max_lead_time_target}}.