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.

Sign up for GitHub

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

Jump to bottom

Build and publish multi-platform developer images #20862

Closed
l0rd opened this issue Dec 1, 2021 · 6 comments
Closed

Build and publish multi-platform developer images #20862

l0rd opened this issue Dec 1, 2021 · 6 comments
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/getting-started Issues related to the getting started samples https://www.eclipse.org/che/getting-started/cloud/ area/plugins 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 Dec 1, 2021 •
edited
Loading

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/ppc64le and linux/s390x versions of the images.
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Dec 1, 2021
@l0rd l0rd mentioned this issue Dec 1, 2021
Open
@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 Dec 1, 2021
@dmytro-ndp dmytro-ndp mentioned this issue Dec 1, 2021
Closed
41 tasks
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. area/plugins area/ci CI build and releases, PR testing, & whitelabel/productization issues area/getting-started Issues related to the getting started samples https://www.eclipse.org/che/getting-started/cloud/ and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 1, 2021
@nickboldt
Copy link
Contributor

nickboldt commented Dec 7, 2021 •
edited
Loading

For downstream developer images (UDI) see https://issues.redhat.com/browse/CRW-2463 and https://issues.redhat.com/browse/CRW-2464 (requires #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.

@che-bot
Copy link
Contributor

che-bot commented Jun 5, 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 Jun 5, 2022
@che-bot che-bot closed this as completed Jun 12, 2022
@l0rd l0rd reopened this Jun 13, 2022
@l0rd l0rd added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 13, 2022
@nickboldt
Copy link
Contributor

nickboldt commented Jul 25, 2022 •
edited
Loading

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. #20799 (comment)

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.

@nickboldt nickboldt removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 25, 2022
@che-bot
Copy link
Contributor

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

l0rd commented Jan 23, 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 Jan 23, 2023
@che-bot
Copy link
Contributor

che-bot commented Jul 22, 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 Jul 22, 2023
@che-bot che-bot closed this as completed Jul 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/getting-started Issues related to the getting started samples https://www.eclipse.org/che/getting-started/cloud/ area/plugins 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nickboldt @l0rd @che-bot