Project

Profile

Help

Issue #6868

closed

Multi-repo-copy has an unintentional requirement for the repo pairs to be provided in a particular order

Added by dalley almost 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Expected Behavior:

The order in which the user specifies their source and destination repositories in the advanced copy API's config object does not matter.

Actual behavior:

The code loops through the pairs of source and destination repositories one by one as it loads them into the solver, decides what to copy, and then creates the new repository versions, which means that when the copy operation is performed for repo pairs early in the list, the solver doesn't know about repos later in the list.

Solution:

Load everything into the solver first, and only after everything has been loaded perform the depsolving + copies.

Also available in: Atom PDF