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

Remove che dev image from release process / delete image (no longer used) #19892

Closed
Tracked by #20218
nickboldt opened this issue May 31, 2021 · 0 comments · Fixed by eclipse-che/che-server#85
Closed
Tracked by #20218
Assignees
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone

Comments

@nickboldt
Copy link
Contributor

nickboldt commented May 31, 2021

Is your task related to a problem? Please describe.

The old che-dev image https://github.com/eclipse-che/che-server/tree/main/dockerfiles/dev is ancient and probably not used anymore.

Describe the solution you'd like

Can we stop publishing it to https://quay.io/repository/eclipse/che-dev?tag=latest&tab=tags and update all doc refs to it to point to new approach using devfile https://github.com/eclipse-che/che-server/blob/main/devfile.yaml ?

Describe alternatives you've considered

Additional context

@nickboldt nickboldt added the kind/task Internal things, technical debt, and to-do tasks to be performed. label May 31, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 31, 2021
@ericwill ericwill removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 31, 2021
@skabashnyuk skabashnyuk added this to the 7.35 milestone Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants