-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark one RHSSO test for PIT server #17204
Merged
+3
−1
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't seen this in
robottelo.yaml
in Jenkins (though it's present inrobottelo.yaml.template
).Do I assume correctly that we depend purely on the validator here?
Maybe rather question for @rmynar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can try available setting
settings.robottelo.cdn == true
here? Or add missing setting in robottelo.yamlCC @rmynar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not say we have to "depend" on validators. But the idea is to maintain validators responsibly (not only in this case) so we can "trust" them.
Relying on default values and modifying the settings only in specific cases seems OK to me. (The rhel_source setting has to be explicitly changed to "internal" usually for interoperability testing - i.e. testing with unreleased RHEL version)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The setting is set in the
.template
configrobottelo/conf/robottelo.yaml.template
Lines 25 to 27 in b7406c0
And yes, in this case, we rely on Dynaconf validators to populate the setting for us, but since validators run unconditionally every time (now even in Robottelo CI/CQ), I share the same view as @rmynar. However, there is no harm in adding an explicit setting in the YAML config. Anyone, feel free to submit a patch.