[patch] Fix Monitor/IoT FVT sequencing to complete before Day2 lifecycle stages#2288
Open
jvaneel-dwivedi wants to merge 1 commit into
Open
[patch] Fix Monitor/IoT FVT sequencing to complete before Day2 lifecycle stages#2288jvaneel-dwivedi wants to merge 1 commit into
jvaneel-dwivedi wants to merge 1 commit into
Conversation
…cle stages Corrects sequencing issue where Monitor/IoT FVT launches were running in parallel with Day2 lifecycle stages (update/upgrade/uninstall). Changes for after-iot scenario (Monitor < 9.2.0): - approval-iot: runAfter launchfvt-iot (was: waitfor-iot) - approval-monitor: runAfter launchfvt-monitor (was: waitfor-monitor) Changes for before-iot scenario (Monitor >= 9.2.0): - approval-monitor-before-iot: remains after waitfor-monitor-before-iot (gates IoT installation, not Day2) - approval-iot-after-monitor: remains after waitfor-iot-after-monitor (gates IoT installation, not Day2) - waitfor-install: added launchfvt-monitor-before-iot and launchfvt-iot-after-monitor dependencies to ensure FVT completion before Day2 stages This ensures all application FVT execution completes before the pipeline transitions into Day2 lifecycle stages, matching the behavior of other applications (Assist, Manage, Optimizer, Predict). Fixes cycle detection error in before-iot scenario where approval tasks needed to gate IoT installation rather than Day2 stages.
jvaneel-dwivedi
force-pushed
the
fix-monitor-iot-fvt-sequencing
branch
from
834c29f to
076d23c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Corrects sequencing issue where Monitor/IoT FVT launches were running
in parallel with Day2 lifecycle stages (update/upgrade/uninstall).
Changes for after-iot scenario (Monitor < 9.2.0):
Changes for before-iot scenario (Monitor >= 9.2.0):
(gates IoT installation, not Day2)
(gates IoT installation, not Day2)
launchfvt-iot-after-monitor dependencies to ensure FVT completion
before Day2 stages
This ensures all application FVT execution completes before the pipeline
transitions into Day2 lifecycle stages, matching the behavior of other
applications (Assist, Manage, Optimizer, Predict).