Rearrange tasks in PER-VM-Validation file. #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lidation.yml file
…al order of other validation tasks
navpreetkaur1098
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why is this PR required?
Currently in per-vm-validation.yaml file, NVME vaildation tasks in Image-Build-Pipeline is skipping because in line 58, the task to check blasklisted drivers is calling the different yaml file.
What changes have been made?
Placed NVME Validation tasks before the Checking the Blacklisted Drivers Task in per-vm-validation.yaml file .
##Link to Pipeline: https://msazure.visualstudio.com/One/_build/results?buildId=76530365&view=logs&j=6a70c712-7fce-512c-c074-140bd0af0e31