che
che copied to clipboard
eclipse-che
Allow to build custom registries using OpenShift rather than local tools
Is your enhancement related to a problem? Please describe.
This is a follow up of https://github.com/eclipse/che/issues/18798. We have documented how to build a custom registry with local tool like docker and buildah. But an OpenShift administrator it would make more sense to use OpenShift rather than a local tool to build the registries.
Describe the solution you'd like
Add an option to build.sh to use OpenShift build rather than buildah and docker. For example using oc start build.
Additional context
That's related to a CRW downstream issue https://issues.redhat.com/browse/CRW-2065
cc @svor it would be nice if you are able to take in next sprint cc @RickJWagner
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.