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

Universal Developer Image enhancements #20799

Open
l0rd opened this issue Nov 19, 2021 · 6 comments
Open

Universal Developer Image enhancements #20799

l0rd opened this issue Nov 19, 2021 · 6 comments
Assignees
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/3-months Epics that are planned to complete in the short term (within 3 months) sprint/current

Comments

@l0rd
Copy link
Contributor

l0rd commented Nov 19, 2021

Is your enhancement related to a problem? Please describe

Issues related to Developers images

  • gh action publishes the wrong "universal base image"
  • there is not automated check for new versions the tools
  • they are not compatible with Red Hat internal image build tool
  • they are not multi-arch
  • there is no PR check against Che samples
  • manual modification of the README.md (tools lists and sizes) is tedious and error prone

Describe the solution you'd like

Additional context

@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 19, 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 Nov 19, 2021
@l0rd l0rd added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/3-months Epics that are planned to complete in the short term (within 3 months) area/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 19, 2021
@nickboldt
Copy link
Contributor

nickboldt commented Nov 22, 2021

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:

  • udi for tech preview support
  • udi for GA support w/ openjdk
  • udi for GA support w/ openj9

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.

@nickboldt nickboldt modified the milestones: 7.42, 7.43 Jan 12, 2022
@l0rd l0rd modified the milestones: 7.43, 7.x (Later, Future, Never) Feb 3, 2022
@max-cx
Copy link

max-cx commented Mar 11, 2022

Please consider adding here the following issue as a sub-task: #21253 .

@nickboldt
Copy link
Contributor

nickboldt commented Jul 25, 2022

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
Copy link
Contributor

che-bot commented Aug 30, 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 Aug 30, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Aug 30, 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 Aug 30, 2023
@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 22, 2024
@che-bot
Copy link
Contributor

che-bot commented Dec 22, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/3-months Epics that are planned to complete in the short term (within 3 months) sprint/current
Development

No branches or pull requests

6 participants