GitRepositoryEnrichier: Could not find source git repo

[voonxx]

Can i safely ignore the warning below?

[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[02:10:04 WRN] [16.0.3] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null

Below is the Repo Mapping config-
"TfsGitRepositoryTool": {
"Enabled": "True",
"Mappings": {
"reponame-1": "reponame-1",
"repox": "repox",
"repoy": "repoy"
}
},

[MrHinsh]

Sure, but its unlikely to map correctly.

Id need the logs to figure out whats hapening.

[voonxxx]

Hi MrHinsh, for the 'Dates must be increasing with each revision' error, the only workaround now is to delete the target migrated workitem and rerun?

[voonxxx]

I have set the MaxRevisions to 10 but seems like it is not picking up and it still looping through all revision history-

"TfsRevisionManagerTool": {
"Enabled": true,
"ReplayRevisions": true,
"MaxRevisions": 10
}

Have i set it in a correct way?

[voonxxx]

The full log contains quite a lot of p&c info, could we scope down a little which info you need so i can take out particular part for troubleshooting?

[voonxxx]

Hi @MrHinsh , is there a way to skip those 'Dates must be increasing with each revision' item and output the workitem id in the error log so the migration process can continue? Currently, it will stop in the middle of the process and i will need to go to target project removed the migrated item and rerun the migration, thinking if there are better way for this.

Thank you.

[MrHinsh]

Thats a good sugestion

[nkdagility-actions-bot[bot]]

Hi there,

ACTION REQUIRED

In order for us to help you will need to provide both the log, and the configration file that you are using.

Generate and Attach Log

Steps:

1. In the Config file, change LogLevel to Debug.
2. Identify a work item ID that exhibits this issue and create a query that only selects this work item.
3. Delete any existing copy of that work item from the target.
4. Run the migration.
5. Comment here with the full Log attached as well as the full (redacted) configration file that you are using.

Your assistance is greatly appreciated!

Thanks, Azure DevOps Migration Tools team