windowsPb: Move msvs2022 install into own block #3248
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #3246 (comment)
The
vs2022_layout_ready
variable does not get registered when theTransfer VS2022 Layout File
task is skipped (due to msvs2022 already being installed). Then when ansible tries to evaluatewhen: (vs2022_layout_ready.stat.exists)
in theGet SHA256 checksum of the file
task it hits an error:Moving the install code into its own block should fix this like it did with #3244