Eclipse Che 7 as a developer tool has evolved to work with some of the most relevant technologies available today: Eclipse Theia, Language Servers, Debug Adapters and even VSCode extensions, all containerized within the IDE. Developer environments have become reproducible, repeatable and consistent across teams of developers - allowing easy integration into your devops toolchain. Working on a kubernetes application has never been easier, just bring your kubernetes application directly into your developer environment.
VS Code is a Desktop IDE with tons of extensions but it is running on your local computer.
Eclipse Che is a developer workspace running in the cloud and allows to use VS Code extensions.
In this session, attendees will be guided on how to use VS Code extensions in Eclipse Che and the benefits that they can have doing that.
The various topics that will be addressed are:
- how to include VS Code extensions into the Eclipse Che registry
Eclipse Che introduces a new kind of developer workspaces that are running directly on Kubernetes and accessible through a web based IDE. The new version of Eclipse Che 7 supports a codified definition of developer tooling needed to work on a project, called “Devfile”.
Devfile provides a declarative abstraction of a replicable developer workspaces, which is inclusive of the runtime environment, the source code of the projects mapped to repositories and the tools, plugins and commands needed to code, build, test, run and debug a project.
Devfile lives with the projects’ source code and follow its lifecycle. It’s easy to create, modify, fork and extend.
In the Cloud-Native world monitoring and distributed tracing are the crucial parts of the service not visible to the naked eye, but vital for DevOps in order to obtain various system metrics, easily investigate underlying issues and identify potential performance bottlenecks. When the cloud IDE is deployed on a cluster it is critical to have enough observability to make sure that the development environment is in a good shape, stable and ready to be used. In this session, we will demonstrate that Eclipse Che running on Kubernetes or OpenShift provides not only a collaborative development environment to the teams but also monitoring and tracing facilities using the cutting edge Cloud-Native stack: Prometheus, Grafana and Jaeger.
If you are a developer interested on cloud native application development and tools, you are probably having trouble following the fast changing world of cloud development tools. You might have questions like:
What is new with Eclipse Che? What does its roadmap look like? What is the relation with the new Eclipse Codewind project and Che? What are the benefits of the new projects under Eclipse Cloud Development (ECD) umbrella that I am missing?
Car manufacturers through the application of new technologies such as IOT, Artificial Intelligence, Machine Learning, Telematics and Big data are connecting cars to their network, external and physical infrastructure, building a connected transportation ecosystem.
Eclipse Kuksa project contain a cloud platform that interconnects a wide range of vehicles to the cloud via in-car and internet connections.
Eclipse Che supports Language Server Protocol (LSP) and it makes possible to support many languages which implement it.
Che uses Theia IDE as a default IDE and it is easy to create new plug-in for Theia IDE with some language and run it in own docker container aka sidecar container. As an example I will take the implementation of LSP for C# - omnisharp-roslyn and create a simple plugin to connect it with Eclipse Che. This session will show you how to create a new plug-in for Theia IDE and how to use it as a remote plug-in in Eclipse Che.
Some of the key difficulties of managing large development teams are ensuring consistency across developer environments, helping new developers get their tooling and dependencies set up, and enforcing consistency among dev, test, and production environments. Eclipse Che solves this problem by provisioning and managing developer environments in the cloud on top of Kubernetes distributions like OpenShift.
Web tools and cloud architectures are great but what does this actually change for developers?
Each contributor currently has to setup his local environment in order to actually contribute to a project. But how about configuring just a single environment for everyone in the cloud? What if your developers didn't even have to be using a specific local environment to work on a product? This is possible using a workspace server dispatching pre-configured containers to your teams, along with all the tools they need.
Do you have a technology that you believe is suitable for cloud native development? Do you want to take advantage of the cloud native IDE. In this talk we are going to show how you can extend Eclipse Che with your technology and make it discoverable to the world.