Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Building Images at WS creation Time
s2i is OpenShift only but we can find another mechanism to build images on Kubernetes.

However I would like to understand is if we really need to do a compilation at runtime. Because it would make workspaces startup slower and it should be worth it.

What's the use case that we don't support currently that we will support if we do the compilation at runtime? In other words what are the benefits?

What are the steps that would be needed to "native-compile jdt.ls" at runtime?  Install a particular JDK? Copy some libs? Do a java compile from jdt.ls source code + some libs?



On Wed, Jul 10, 2019 at 10:57 AM Ilya Buziuk <ibuziuk@xxxxxxxxxx> wrote:
So my idea is to run a s2i build when a workspace is created or when it's configuration is changed. The s2i build would native-compile jdt.ls together with the bundles that need to run inside it. The outcome will be the "Java support" sidecar image.

Sounds interesting but s2i is OpenShift specific framework. How this would work in the Kubernetes world?

On Wed, Jul 10, 2019 at 10:33 AM <tmader@xxxxxxxxxx> wrote:
Hi folks,

I had an idea I'd like to run by the folks more familiar with workspace creation than me: we've had conversations about native-compiling jdt.ls-based Che 7 plugins. The thing that is keeping us from doing this right now is the dynamic nature of jdt.ls: it is a OSGI application that loads stuff at runtime. In short, the whole-world assumption that native compilation relies does not hold in our case. I know that right now we're only shipping Che 7 plugins that have a fixed set of jdt.ls plugins, but I still hope we can get to a world where we we can dynamically assign VS Code extensions to the proper sidecar image in the future, so I'd like to find a solution that would work in that world.
So my idea is to run a s2i build when a workspace is created or when it's configuration is changed. The s2i build would native-compile jdt.ls together with the bundles that need to run inside it. The outcome will be the "Java support" sidecar image.

Any comments on this? Is this hot shit or a steaming pile of the same?

/Thomas
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev


--

ILYA BUZIUK

SENIOR SOFTWARE ENGINEER

Red Hat

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top