ci/ui: automate ui-extension upgrade #1127
Merged
Conversation
This file contains 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
0ce4b94 to
fedcb7e
Compare
4a7c3ab to
cfda403
Compare
cfda403 to
75558dd
Compare
ldevulder
approved these changes
Dec 19, 2023
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.
Address partially #1094 by adding an upgrade test of the Elemental UI Extension.
After a lot of debugging, I add extension upgrade in K3S tests only, I tried with RKE2 but it added flakiness.
Verification runs
UI-K3s-OS-Upgrade-RM_head_2.8 ✅ - Failed in
Store logsbecause I disabled proxy for the testUI-K3s-OS-Upgrade-RM_head_2.7 ✅ - Failed in
Store logsbecause I disabled proxy for the testUI-K3s-OS-Upgrade-RM_Stable ✅ - Failed in
Store logsbecause I disabled proxy for the testUI-K3s-RM_head_2.7 ✅
UI-K3s-RM_head_2.8 ✅