-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Clean up che-theia build: rely on multistage build as much as possible. #18969
Comments
I would say it's not so important as dogfooding is #1 priority and everything is setup in theia-dev image. |
If we download the dependencies in the che-theia-dev build, it would benefit dogfooding UX: it won't redownload the dependencies each time you create a new workspace. |
well if it's to address caching of dependencies, the title is wrong. I think time should be spent on improving dogfooding, not setuping a local build as for development mode you'll probably loose too many times on all changes you do. |
anyway, on your local computer, you could just have used quay.io/che-theia:dev image as well |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Is your task related to a problem? Please describe.
I tried to build che-theia from my local laptop but failed :
yarn
commandg++
We are already doing most of the build in docker multistage builld, so I don't see any reason to keep this line:
https://github.com/eclipse/che-theia/blob/39b67042da45484b53af20ad1759ddaeaf19762c/build.sh#L16
Describe the solution you'd like
Remove the line https://github.com/eclipse/che-theia/blob/39b67042da45484b53af20ad1759ddaeaf19762c/build.sh#L16
And make sure everything is done and still working in existing multistage build.
Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: