[DO NOT MERGE] Build CheCode editor image to test PR-363#769
Conversation
…ainers Signed-off-by: Roman Nikitenko <rnikiten@redhat.com>
Opened to create a CheCode editor image to test: - eclipse-che/che-machine-exec#363 <!-- Please include any related issue from the Eclipse Che repository (or from another issue tracker). --> - [ ] the PR contains changes in the [code](https://github.com/che-incubator/che-code/tree/main/code) folder (you can skip it if your changes are placed in a che extension ) - [ ] the corresponding items were added to the [CHANGELOG.md](https://github.com/che-incubator/che-code/blob/main/.rebase/CHANGELOG.md) file - [ ] rules for automatic `git rebase` were added to the [.rebase](https://github.com/che-incubator/che-code/tree/main/.rebase) folder <!-- This is an auto-generated comment: release notes by coderabbit.ai --> * **Chores** * Updated the container image used during the build assembly process to a newer version, which may improve build reliability and consistency. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Victor Rubezhny <vrubezhny@redhat.com>
|
Hi! I'm che-ai-assistant — I help with your pull requests. Available commands:
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe machine-exec assembly now uses a PR-specific image and packages separate binaries for ubi8, ubi9, and musl under their respective checode directories. Initialization copies all Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant MachineExecImage
participant RootfsAssembly
participant InitContainer
participant ChecodeVolume
participant VolumeEntrypoint
participant MachineExec
MachineExecImage->>RootfsAssembly: Supply che-machine-exec binaries
RootfsAssembly->>ChecodeVolume: Populate distribution-specific checode directories
InitContainer->>ChecodeVolume: Copy /checode-* content into /checode/
VolumeEntrypoint->>MachineExec: Start ./machine-exec with MACHINE_EXEC_PORT=3333
MachineExec->>ChecodeVolume: Run from the selected checode directory
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Pull Request images published ✨ Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-769-amd64 |
What does this PR do?
Opened to create a CheCode editor image to test:
eclipse-che/che-machine-exec#363
What issues does this PR fix?
How to test this PR?
Does this PR contain changes that override default upstream Code-OSS behavior?
git rebasewere added to the .rebase folderSummary by CodeRabbit