Can't find working schema for configuration.json in v16.2.10 – deprecated schema and upgrade action both fail #2924
Unanswered
JavierGonzalezMartos
asked this question in
Q&A
Replies: 1 comment 3 replies
-
I was able to validate the schema online ![]() Do you know if your network might be blocking access to the schema? Proxy server maybe? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm trying to use Azure DevOps Migration Tools v16.2.10 to migrate work items between two Azure DevOps organizations. However, I'm running into issues with the configuration schema.
When I try to execute the tool with a
configuration.json
file using the schema fromhttps://devopsmigration.io/schema/configuration.schema.json
, I get the following error:"Error when resolving schema reference 'https://devopsmigration.io/schema/configuration.schema.json'
Unexpected token encountered when reading value for 'prefixItems'. Expected StartArray, got StartObject."
I also tried using the old v1 schema and then running the
upgrade
action, but that also fails due to version-related errors.I’ve followed the official documentation but it’s unclear which schema version should be used with the current version of the tool. Even the latest schema seems to fail validation or execution.
Here’s what I’ve tried so far:
--skipVersionCheck
→ bypasses version check, but processors and endpoint structures still throw errorswinget
, but installation shows hash mismatch and doesn't run properlyCould someone please share:
configuration.json
example that works with version 16.2.10 for migrating work items?$schema
URL to use?Endpoints
as arrays,FieldMaps
moved out ofCommonTools
, etc.)Thanks in advance for any help you can provide!
Beta Was this translation helpful? Give feedback.
All reactions