Wave Page

Open a wave from the Migration Plan rail. The page is there before the move runs. It shows where the wave's repositories land, the Ready to move when list, the plan's features as they apply to this wave, and a stage strip.

Opening a wave

You need the Migration Assistant manage permission. The Migration Plan is available on CodeCargo plans that include it. If you do not see it, contact your CodeCargo administrator.

Stages

The stages come from what the plan does, not from the wave's dates. A short window still shows every stage that applies. A wave with no dates says No dates yet wherever a date would show.

The move step shows Move repositories, and Rewire pipelines when the plan rewires.
The convert step shows Converge callers, and Building blocks ready when a source builds building blocks.
A wave with one window shows every stage that applies, together.

Select a stage to see its plan and where the wave sits. The stage stays in the address, so you can reload or share the link. A button opens the next stage. A stage that runs later says what will happen and stays read-only.

The Wave 1, Data platform page: its move and convert dates, the Ready to move when list, its features, and a stage strip with Move repositories selected and Rewire pipelines next, above the expected move time, the longest repository and the move window.

Features for This Wave

The features row shows SLSA, CargoWall, the conversion style when the wave has pipelines, the replacements, and the plan's directives. A value that belongs to this wave, rather than the plan, is marked (this wave). That includes off (this wave).

Plan features are set on Set Up the Plan.

Repositories

The page shows the wave's repositories and where they land.

It counts how they move, including Migrate again, Needs a fix, Dry run pending, and Not copied yet. Needs a fix is a dry-run copy that needs a fix. Dry run pending is queued or still copying. Not copied yet has not been copied. Finish that copy on Dry Run.

It also counts repositories that use Git LFS, and repositories not checked for Git LFS yet.

Move Repositories

This stage shows how long the move is expected to take, the repository expected to take the longest, and the move window. It also shows the expected time for each destination org. See How long a move takes.

Rewire Pipelines

Repositories in an earlier wave that reference this wave's repositories kept those references on Azure DevOps. They are rewired again once this wave lands. The stage lists those earlier waves.

For how the dry run's decisions split, see Prepare the Rewire.

Migration Plan

Follow the plan journey, the recommended next step, and the summary of what is left.

Schedule Waves

Date the waves and compare each move with its window.

Dry Run

Copy repositories into the sandbox and resolve a failure.