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

[Cross-Project Epic] Build all Che images using Travis (multiarch support) #19688

Closed
nickboldt opened this issue Apr 27, 2021 · 3 comments
Closed

[Cross-Project Epic] Build all Che images using Travis (multiarch support) #19688

nickboldt opened this issue Apr 27, 2021 · 3 comments
Labels
area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Apr 27, 2021 •
edited
Loading

Is your task related to a problem? Please describe.

Since we can't build all the Che images w/ qemu + buildx, as it's unstable on s390x, it's been suggested we instead build IBM hardware-based images (s390x and ppc64le) using Travis, as there is IBM hardware available for free for open source projects.

Describe the solution you'd like

Develop a PoC that scripts:

  • nightly / CI builds of che images w/ Travis
  • weekly release builds of che images w/ Travis

In both cases, images should be published to quay.io in existing org / image paths, using -arch suffixes like :7.32.0-s390x.

See examples here:

Hardest ones to do are likely:

  • che server (maven: server assembly + container image)
  • che-theia (node: three container images produced)

Complete list:

  • Configbump + Traefik
  • Operator + Operator-metadata
  • Jwtproxy
  • Plugin broker artifacts + Plugin broker metadata
  • Dashboard
  • Server
  • Devfile registry, plus 17 sidecars
  • Machine exec
  • Theia, theia-dev, theia-endpoint
  • Plugin registry
  • Devworkspace controller (DWO)
  • Devworkspace che operator (DWCO)

Describe alternatives you've considered

Additional context
@nickboldt nickboldt added kind/task Internal things, technical debt, and to-do tasks to be performed. area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 labels Apr 27, 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 Apr 27, 2021
This was referenced Apr 27, 2021
Closed
Closed
@skabashnyuk skabashnyuk added area/ci CI build and releases, PR testing, & whitelabel/productization issues and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Apr 28, 2021
@nickboldt nickboldt mentioned this issue May 6, 2021
Merged
9 tasks
@prabhav-thali prabhav-thali mentioned this issue May 14, 2021
Merged
@vibhutisawant vibhutisawant mentioned this issue Jun 7, 2021
Merged
@nickboldt nickboldt mentioned this issue Jul 20, 2021
Merged
9 tasks
@nickboldt nickboldt added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) labels Jul 20, 2021
@nickboldt nickboldt changed the title Build che images using Travis [Cross-Project Epic] Build all Che images using Travis (multiarch support for s390x, ppc64le, arm, amd) Jul 20, 2021
@nickboldt nickboldt changed the title [Cross-Project Epic] Build all Che images using Travis (multiarch support for s390x, ppc64le, arm, amd) [Cross-Project Epic] Build all Che images using Travis (multiarch support) Jul 20, 2021
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Jul 20, 2021
@nickboldt nickboldt mentioned this issue Aug 5, 2021
Closed
@nickboldt
Copy link
Contributor Author

Initial PoCs are:

@nickboldt
Copy link
Contributor Author

nickboldt commented Aug 20, 2021 •
edited
Loading

Machine exec build for PRs and :next builds is merged - details.

image

Next steps:

  • enable machine exec travis build for release (7.35.1); let it run for 3 weeks (including 7.36.0); collect speed/performance data
  • enable theia build for PR, branch check, :next, and release (7.35.1 if possible); also let it run through 7.36.0 and collect perf data
  • if everyone agrees, disable GH actions for builds/checks and use only Travis
  • repeat the above steps for the other 20 Che projects :)

@benoitf benoitf added the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Sep 14, 2021
@nickboldt nickboldt mentioned this issue Sep 16, 2021
Merged
9 tasks
@l0rd l0rd removed the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Sep 28, 2021
@nickboldt nickboldt added the severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. label Sep 28, 2021
@che-bot
Copy link
Contributor

che-bot commented Mar 27, 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 Mar 27, 2022
@che-bot che-bot closed this as completed Apr 3, 2022
@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 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/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@nickboldt @benoitf @l0rd @skabashnyuk @che-bot @max-cx