search

eclipse-che / che

Kubernetes based Cloud Development Environments for Enterprise Teams
http://eclipse.org/che
Eclipse Public License 2.0
6.93k stars 1.19k forks source link

Universal Developer Image enhancements #20799

Open l0rd opened 2 years ago

l0rd commented 2 years ago

Is your enhancement related to a problem? Please describe

Issues related to Developers images

Describe the solution you'd like

Additional context

nickboldt commented 2 years ago

Rework developers images to make them compatible with Red Hat internal image build tool (aka brew)

Note: downstream in https://issues.redhat.com/browse/CRW-2463 and https://issues.redhat.com/browse/CRW-2464 we are required to have 3 images:

Or, we need a way to differentiate which devfile tiles in the dashboard are GA-supported / tech-preview. Perhaps a red outline or a ribbon on the tiles? Could also use this mechanism to differentiate Che samples from CRW samples.

max-cx commented 2 years ago

Please consider adding here the following issue as a sub-task: https://github.com/eclipse/che/issues/21253 .

nickboldt commented 1 year ago

Or, we need a way to differentiate which devfile tiles in the dashboard are GA-supported / tech-preview. Perhaps a red outline or a ribbon on the tiles? Could also use this mechanism to differentiate Che samples from CRW samples.

We now have a way of labelling devfiles as "tech preview" or "community" via a label.

image

udi for GA support w/ openj9

And there's no longer openJ9 images downstream (https://issues.redhat.com/browse/CRW-3048).

So, at this point we could consider having the same devspaces-samples projects in both Che and Dev Spaces, augmented by some projects that are ONLY upstream.

This would reduce the sample list so we don't have slightly different samples for the same languages in up vs. down, and would make it more feasible to use the same (or a more-closely-aligned, less-forking-needed) UDI image in both up and downstream.

che-bot commented 10 months ago

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.

l0rd commented 10 months ago

/remove-lifecycle stale