CI build runners: server migration for Nigerian teams

Inventory the source and destination

Record the ci build runners versions, data locations, access rules, scheduled jobs, integration endpoints and domain records. Confirm capacity and software compatibility on the destination. Keep the source recoverable until the destination has passed the agreed checks.

Drain running jobs before moving runners. Register the target, run a non-production pipeline and confirm the old runner cannot accept duplicate work.

Rehearse before the live cutover

Preserve runner configuration and securely managed secrets, while treating rebuildable caches as optional. Keep source and release artefacts in their appropriate durable stores.

Make a trial copy to an isolated target and run this acceptance check: A clean build produces the expected artefact and a failed job cannot modify the production server. Disable or redirect customer-facing notifications, payment actions and scheduled jobs during rehearsal so testing does not duplicate live work.

Control the final writes

Choose a documented write-freeze or synchronisation procedure suited to the application. Assign one person authority to begin the cutover. Track the final successful copy, the point when new writes are allowed and the single system responsible for background processing.

Validate traffic and business records

Check build duration and peak concurrent job memory after the move, together with counts or reference records that demonstrate data consistency. DNS caches may continue sending some clients to the old endpoint, so observe both systems during the transition instead of assuming a record change is instant.

If the destination fails the business check, investigate the workload-specific failure path: Inspect job logs, disk growth and dependency-download failures. Raising concurrency can create slower builds when jobs compete for the same resources.

Define rollback before reopening

A rollback is straightforward only while the source still represents the authoritative data. Once the destination accepts writes, switching traffic back without reconciliation can discard new work. State the rollback deadline, the triggers and the procedure for preserving changes in advance.

For a Nigerian team, agree a maintenance window around actual working hours and customer demand. Verify access from the office and mobile networks, then retain the old environment according to a documented review and deletion schedule rather than an arbitrary promise of zero downtime.

Server migration worksheet

Use these prompts in your project notes. Replace general targets with measurements and an accountable owner.

Can ci build runners move with no downtime?

That depends on the application, replication method and consistency requirements. A rehearsed maintenance window is often clearer than an unsupported zero-downtime promise. Estimate the final copy and validation time from a trial, then agree the interruption with the people affected.