improvement(ci): route maintenance tests in backend IT#10510
Open
FANNG1 wants to merge 2 commits intoapache:mainfrom
Open
improvement(ci): route maintenance tests in backend IT#10510FANNG1 wants to merge 2 commits intoapache:mainfrom
FANNG1 wants to merge 2 commits intoapache:mainfrom
Conversation
Code Coverage Report
|
f1094d8 to
f10c73b
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
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.
What changes\n- trigger Backend Integration Test for changes\n- detect maintenance-only changes in backend IT workflow\n- run only maintenance integration tests for maintenance-only changes\n- run existing backend IT together with maintenance tests for non-maintenance-only changes\n\n## Why\n- verify backend IT routing behavior for maintenance changes\n\n## Test\n- workflow YAML parsed locally with Ruby Psych\n- prepared stacked validation branches for maintenance-only, mixed, and non-maintenance scenarios