che
che copied to clipboard
eclipse-che
Build and publish multi-platform developer images
Is your enhancement related to a problem? Please describe
We are currently only building linux/amd64 developer images.
Describe the solution you'd like
- Identify supported platforms for every tool included in the image and add specify it in a devtools.json file
- Adapt the asset build/download script to only process the tools that are supported on current platform
- Use gh docker build push action to build and push
linux/amd64,linux/arm64,linux/ppc64leandlinux/s390xversions of the images.
For downstream developer images (UDI) see https://issues.redhat.com/browse/CRW-2463 and https://issues.redhat.com/browse/CRW-2464 (requires https://github.com/eclipse/che/issues/19953 )
If upstream is not multiarch (because we can't use buildx on Z) that should not prevent downstream from being multiarch. Note too that downstream does not support arm64.
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.
Downstream no longer has to split between TP and GA as we have added labels into the dashboard. There are also no openj9 images anymore. https://github.com/eclipse/che/issues/20799#issuecomment-1194054260
So while we still need multiarch downsteam, the same Dockerfile might be possible for up and downstream.
We might still filter out some languages that are not supported downstream.
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.