[patch] move cvscan to finally block in fvt-iot pipeline #818
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.
There is a conflict in test cases between cvscan and podtemplates. Resources need to be reset before cv-scan, hence, moving the cv-scan to finally block in the fvt-iot pipeline.
Infact, moved cv-scan task in all fvt pipelines to finally block and ran fvt for core and iot. Few test cases failed in core, hence, as part of the below bug, updating only fvt-iot pipeline at the moment. Will create a new task to address for all other pipelines.
Ref bug (Jira): IBMIOT-238
Test: Ran fvt-personal with changes
Branch: pfvtiotb238
CLI version: 7.16.1-pre.iotb238
FVT_VERSION_IOT=1.3.2-pre.iotb238
https://<dashboard_url>/tests/pfvtiotb238
Builds (2193 & 2198)