This repository was archived by the owner on Feb 6, 2025. It is now read-only.
Remove addon upgrade test from pr pipeline #1299
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
Remove test that is not part of the minimal functionality to be tested for approving a PR. Signed-off-by: Pablo Chacin <pchacin@suse.com>
jordimassaguerpla
approved these changes
Aug 3, 2020
mkoci-suse
pushed a commit
that referenced
this pull request
Feb 6, 2025
…om-pr Remove addon upgrade test from pr pipeline
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 needed?
The PR pipeline tests only check the changes introduced the PR do not break the ability to deploy a new cluster. The
addon upgrade applytest does not comply with this objective.Fixes https://github.com/SUSE/avant-garde/issues/1867
What does this PR do?
Removes the
prmark from thetest_upgrade_addon_applytest to prevent its execution in the PR pipelineMerge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises: