Review Pipeline Families

Review Pipeline Families

The plan's Review pipeline families step lists the families for the pipelines the plan converts. A family groups pipelines that belong together. You review the largest families one by one, then accept the rest as a batch.

Coverage shows how many pipelines the plan converts, how many of those are in a family, and how many are in no family. Pipelines in no family are part of that coverage, not a row in the table. The step also shows how far review has come. The list includes the families already found for these pipelines.

Start the Analysis

The step appears before any families exist, once the plan has pipelines to convert and family analysis is available to your organization. You do not need waves scheduled first. If the plan has pipelines to convert and you still do not see the step, contact your CodeCargo administrator.

Until there are families, the page shows an analysis card instead of the table. Start the analysis from the card. It runs once for each source whose pipelines the plan converts, over that source's imported pipelines. The card lists each source and its latest run, and says when a run failed or found no families. A source that is already running is left alone. A source with an import still open is left out. Start again once that import finishes. Families appear as each run finishes, and the page updates while a source is still running.

With no families yet, the step is Needs you before any run and after a failed or stopped run, In progress while a run is going, and Done when every source's run found no families. After families exist, the table replaces the card. Under the coverage, Last analyzed shows when the latest run finished, and Analyze again starts another pass.

The Families Table

The table lists families largest first, one page at a time, so a large estate stays usable. Each row shows the family's name and source, how many of the plan's pipelines it holds, how many repositories those pipelines are in, the first wave they are in, how many waves they span, and whether it is reviewed.

The largest families are a quarter of the families, always at least 1 and at most 20. Those are the ones you review one by one. Every other family can be reviewed on its own or accepted with the rest.

Filter and Sort

Search the list, then narrow it. Filters combine, so a family has to match every filter you set. You can filter by wave, including families that still have pipelines in no wave, by project, and by whether the family is reviewed.

Each option shows how many families it holds given your other filters. That count leaves out the filter you are looking at, so the other options still show how they split the list. Sort by size, by name, or by the first wave, soonest first.

Where a Family's Pipelines Are

Select a family to see its description and where its pipelines are: by plan wave, and by Azure DevOps project. Pipelines in no wave, and pipelines with no repository in the plan, are counted apart.

Mark Families Reviewed

Mark each of the largest families reviewed on its own. Accept the smaller families as a batch to mark them reviewed, or mark or clear any family on its own.

The step is done when every family is reviewed.

If the plan or its families changed since you loaded the list, the mark does not apply. Check the list and try again.