update RedHat example Dockerfile #7047
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
alexrashed
force-pushed
the
fix-redhat-image-build
branch
from
407950d
to
2a621b4
Compare
alexrashed
force-pushed
the
fix-redhat-image-build
branch
from
c6cebf9
to
c437d5f
Compare
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.
This PR tries to revive our RedHat Dockerfile example located in
Dockerfile.rh.The workflow has been deactivated due to several issues over the time (python upgrades, filesystem changes, certain non-redhat compatible installers,...).
With our new installer structure (introduced in #6783), these issues can now be addressed.
This PR also changes the trigger of the pipeline from being executed on every master build to be executed on a schedule (every week) since it only tests the latest dev releases against each other (and therefore doesn't directly test the latest commit on the master).
Unfortunately, the pipeline can't really be tested (since it had no workflow trigger before). I tested the steps locally though.