initial commit of a new EE build process #172
Closed
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
currently we rely on EE images that are maintained in external repos, which requires coordination and time in order to make updates to our EE images. this is an initial take on adding a local build process, which will allow us more granular control over any EE images we want to use with the demo content. note that one of the requirements for using the redhat.openshift collection is the openshift-clients binary RPM. adding it to the repo works but it slows down clone operations, so it may be worth using git-lfs for large file management. using git-lfs would mean that developers would need to install it locally, so we should probably discuss it before we move to that model.
|
we could also close #115 with this PR. we'd need to discuss how many version-specific EEs we maintain over time, maybe something like N-2? |
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.
currently we rely on EE images that are maintained in external repos, which requires coordination and time in order to make updates to our EE images. this is an initial take on adding a local build process, which will allow us more granular control over any EE images we want to use with the demo content. a complementary quay.io organization has been set up for storing the images. the build process is manual for now and described in the README. if we like the idea of moving in this direction, over time we can look at a pipeline build process.
note that one of the requirements for using the redhat.openshift collection is adding the openshift-clients binary RPM to the EE. adding the RPM to this repo works but it slows down git operations like cloning, so it may be worth moving to git-lfs for large file management. using git-lfs would mean that developers need to install it locally, so we should probably discuss it before we move to that model.