Add proxy retail test to qe update to automatically #1290
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 does this PR change?
In the current SLE update pipeline, the retail proxy feature is not being executed, which means that bind and DHCP packages are not automatically tested. To eliminate the need for manual testing of a feature that is already validated in Build Validation, this PR introduces the option to run the retail proxy feature. Since we do not have a terminal or build clients available, the scope is limited to running
features/build_validation/retail/proxy_traditional_branch_network.feature
. The option will be disabled by default and should be enabled only when relevant packages are involved.Ideas for Further Improvement
Deploying sle15sp4_terminal and sle15sp4_buildhost as additional clients could enhance testing for TFTP packages, potentially saving time. However, this would require changes to the infrastructure. @Bischoff, is there enough space on PRV to accommodate these two additional clients?