Skip to content
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

Allow to build custom registries using OpenShift rather than local tools #20177

Closed
l0rd opened this issue Jul 22, 2021 · 9 comments
Closed

Allow to build custom registries using OpenShift rather than local tools #20177

l0rd opened this issue Jul 22, 2021 · 9 comments
Assignees
Labels
area/devfile-registry area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 22, 2021

Is your enhancement related to a problem? Please describe.

This is a follow up of #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

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/devfile-registry area/plugin-registry severity/P1 Has a major impact to usage or development of the system. sprint/next labels Jul 22, 2021
@l0rd
Copy link
Contributor Author

l0rd commented Jul 22, 2021

cc @svor it would be nice if you are able to take in next sprint
cc @RickJWagner

@svor svor mentioned this issue Jul 22, 2021
34 tasks
@svor svor self-assigned this Jul 28, 2021
@svor svor mentioned this issue Aug 12, 2021
30 tasks
@svor svor mentioned this issue Sep 8, 2021
26 tasks
@svor svor removed the sprint/next label Sep 8, 2021
@svor svor mentioned this issue Sep 23, 2021
25 tasks
@svor svor removed the sprint/next label Sep 29, 2021
@RickJWagner
Copy link
Contributor

/label px-visited

@che-bot
Copy link
Contributor

che-bot commented May 30, 2022

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2022
@svor
Copy link
Contributor

svor commented May 30, 2022

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2022
@che-bot
Copy link
Contributor

che-bot commented Nov 26, 2022

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 26, 2022
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 28, 2022
@che-bot
Copy link
Contributor

che-bot commented Jun 7, 2023

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 7, 2023
@che-bot che-bot closed this as completed Jun 14, 2023
@l0rd l0rd reopened this Jun 15, 2023
@l0rd l0rd removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2023
@che-bot
Copy link
Contributor

che-bot commented Dec 12, 2023

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 12, 2023
@svor
Copy link
Contributor

svor commented Dec 12, 2023

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 12, 2023
@che-bot
Copy link
Contributor

che-bot commented Jun 9, 2024

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2024
@che-bot che-bot closed this as completed Jun 16, 2024
@svor svor reopened this Jul 3, 2024
@che-bot che-bot closed this as completed Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-registry area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants