-
-
Notifications
You must be signed in to change notification settings - Fork 372
Open
Labels
Description
Version
- I confirm that I am using the latest version
Source Version
Azure DevOps Server 2019
Target Version
Azure DevOps Service
Relevant configuration
My configuration contains :
"TfsChangeSetMappingTool": {
"Enabled": false
}
Relevant log output
After the upgrade, I have this:
Validation errors (deduplicated & filtered):
Path: MigrationTools.CommonTools.TfsChangeSetMappingTool.ChangeSetMappingFile
- (Ln 662, Pos 36) Type: Invalid type. Expected String but got Null.
Total unique validation errors after filtering: 1
NOTE: A single missing property can trigger multiple branch (anyOf/allOf) mismatches. Fix the root cause lines above first.
What happened?
I'm running an upgrade and after the upgrade, the tool is not starting anymore complaining that TfsChangeSetMappingTool.ChangeSetMappingFile cannot be null.
The upgraded file contains this:
[...]
"TfsChangeSetMappingTool": {
"Enabled": false,
"ChangeSetMappingFile": null
},
[...]
This is wrong and "ChangeSetMappingFile" should not be emitted
Debug in Visual Studio
- Visual Studio Debug
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
To do