-
-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: ShouldCreateMissingRevisionPaths setting is ignored / always set to false #1876
Comments
I don't see anywhere in the logic that it gets set to "false". ADO is down right now so I will have to debug later. |
Sooooo.... the |
That is another issue, but I've found out a few more details. It looks like in my case the TestPlansAndSuitesMigration context is overriding the property (line 87).
I've added the static ShouldCreateMissingRevisionPaths property and then property is never changing to false. |
You can use the
and then on the processors use:
This does not happen when you use these processors separately; they are not expected to be run together. We should probably move to only using |
This is now resolved in v15 |
Version
Source Version
Azure DevOps Server 2020
Target Version
Azure DevOps Server 2020
Relevant configuration
Relevant log output
No response
What happened?
Repo Steps:
Expected behavior:
My expectation is that because ShouldCreateMissingRevisionPaths is set to true, all missing area paths will be created as part of the migration.
Debugging analysis:
As part of my debugging session, I've figured out that in file TfsNodeStructure -> ProcessorExecutionBegin -> Options.ShouldCreateMissingRevisionPaths is always set false even if the value is set to true in my mapping file.
If you set the option to true in source code then everything works as expected.
As the moment my test code looks like:
Debug in Visual Studio
The text was updated successfully, but these errors were encountered: