Releases: eclipse-che/che
Eclipse Che 7.53.0
Major Enhancements
Add an IDE-only workspace sample in the Dashboard getting started (without project)
A new example has been added in the Getting Started section of Eclipse Che Dashboard that allows users to start the IDE without any source code project. Git repositories can be opened from the IDE once the workspace is started.
Major Bug Fixes
Adding a container registry from Dashboard User preferences doesn't work
If a user added a container registry credential in Eclipse Che User Dashboard, that credential was not used to pull images from the registry resulting in workspaces failing to start.
Theia VS Code extensions updates
Eclipse Che 7.52.0
Major Enhancements
Allow to set environment variables into Eclipse Che core components using CheCluster
An admin can now specify arbitrary environment variables that will be applied to the containers of the core components of Eclipse Che. Those environment variables can be specified in the CheCluster
Custom Resource.
Major Bug Fixes
User is not redirected to the IDE even if the workspace has started successfully
Sometimes the dashboard was not redirecting the user to the IDE.
Che Operator sometimes deploys DevWorkspace Operator even if it is present in the cluster
On OpenShift the DevWorkspace Operator is managed by OLM as a Eclipse Che dependency. As a consequence Eclipse Che Operator should not manage the DevWorkspace Operator when it's installed on OpenShift. But that was not the case and it has been fixed.
Use namespace API instead of project API to set nodeSelector and podTolerations annotations
Use namespace API instead of project API to set nodeSelector and podTolerations annotations
Eclipse Che 7.51.0
Major Enhancements
Add a VS Code extension that reports if the editor is actively used
The Che workspaces VS Code now includes an extension that tracks and report the IDE activity. That can be used by che-machine-exec to automatically stop a workspace for inactivity/run timeout.
Users can select the editor when starting an example for Che dashboard
When starting a workspace from Che samples page in user dashboard it's possible to select the editor that will be included in the development environment.
Allow admins to change workspaces inactivity and run timeout
Administrators can specify the timeout for inactivity and running workspaces with the CheCluster
spec.devEnvironmentfields
secondsOfInactivityBeforeIdlingand
secondsOfRunBeforeIdling` respectively. The default values are 30 minutes and -1 (no timeout) respectively.
Eclipse Che 7.50.0
Major Enhancements
Simplify Eclipse Che configuration format (CheCluster API v2)
CheCluster
Custom Resource Definition has been updated to reflect that changes introduced with the switch to the DevWorkspaces. The result is a shorter and simpler configuration file to maintain for Eclipse Che administrators.
When a workspace is idled for inactivity user is redirected to Che dashboard
When a workspace is stopped after an inactivity now the users are redirected to the Dashboard. Previously a 503 error was displayed.
Allow an admin to specify Che default editor and containers
Che administrators can now configure the default editor (Theia, VS Code, IntelliJ or PyCharm) and the default container. Those defaults are used when the developer doesn't specify an editor or doesn't specify a devfile. The configuration can be done in the CheCluster
Custom Resource in the the workspaces
section using the just introduced defaultComponent
and defaultEditor
fields.
JetBrains IDEs running in a Che workspace autodetects the URL of a running application
As Visual Studio Code and Theia, now IntelliJ and PyCharm can detect when an application running in a Che workspace is listening to a given port and prompt the user to open the application URL. This is true even if the application has not been specified as an endpoint
in the Devfile: a generic endpoint is assigned to applications that doesn't have a dedicated one.
oAuth-proxy enhancements for Azure AKS deployments
Some enhancements needed to deploy Che on Azure AKS has been contributed by @karatkep. Thank you for your contribution.
Major Bug Fixes
When using Visual Studio Code as a Che editor, the lines in the terminal are truncated and overlap
In VS Code terminal lines are not truncated anymore.
Eclipse Che 7.49.0
Major Enhancements
Current directory when opening a terminal in Che-Code should be the project folder
The current directory when opening a terminal in Che-Code should be the root folder of the workspaces project. The path of that folder is set in the environment variable PROJECT_SOURCE.
Support Devfile commands in Che-Code · Issue #21030 · eclipse/che
Che-Code translates commands described in a Devfile as Visual Studio Code tasks. That makes it easier for developers to run predefined commands from within the IDE.
Major Bug Fixes
No major bug fixes this release.
VS Code extensions Updates
Eclipse Che 7.48.0
Major Enhancements
Default Che URL prefix should be eclipse-che rather than che-eclipse-che
The default URL is now shorter and doesn't have the name che repeated twice in it. The URL prefix doesn't depend on the Kubernetes namespace where Che is deployed anymore but is always in the format eclipse-che.<cluster-domain>
.
Always use OAuth flow to authenticate user against Git services (GitHub, Gitlab and Bitbucket) when a workspace starts
When starting a workspace for the first time users are prompted systematically to authenticate against the Git service provider if the OAuth flow has been enabled by the administrator. That allows to always inject personal tokens with git credentials in workspaces. That was done for private repositories only and it's now extended to any repository. The git services providers that are supported are GitHub SaaS, Gitlab on-prem and Bitbucket on-prem.
Include a link to go back to the dashboard in the workspace loading page
The workspaces loading page didn't had any link to get back to the dashboard. Now it's possible to click on a link on the top left of the page to get back to the dashboard and on a link that is shown when an error occurs.
Major Bug Fixes
No major bug fix in this release
VS Code extensions Updates
No VS Code extension update in this release
Eclipse Che 7.47.0
Major Enhancements
No major enhancement has been merged this month.
Major Bug Fixes
After login users get redirected to the dashboard although they used a link to start a workspace
With this fix users will be correctly redirected to the workspace after authentication.
VS Code extensions Updates
Update VS Code extension che4z-explorer-for-endevor to v1.1.0
Eclipse Che 7.46.0
Major Enhancements
Updating Che Dashboard and Che-Theia Node.js versions
Node.js 12 will go EOL on 2022-04-30, Che dashboard has been updated to Node.js v16 and Che Theia to v14 (for VS Code extensions compatibility).
Pair programming: enable usage of CodeTogether propsed API for better UX
This improve the UX of CodeTogether VS Code Extension in a Che workspace and for instance allows to share the terminal.
Add a resource monitoring extension for VS Code based Che workspaces
The resource monitoring extension tracks memory and cpu usage of the different components of a Che workspace. This is now a built-in extension of Che Code, the build of VS Code (Code OSS) for Che workspaces.
Major Bug Fixes
Start an ephemeral workspace fails
The fix allows to start workspaces in ephemeral mode, and therefore faster.
Chectl server:logs should get logs from all Che containers
With this fix Che command line tool chectl
is downloading the logs of all the server components of Che, including the gateway.
VS Code extensions Updates
#1236 Update VS Code extension che4z-explorer-for-endevor to v1.0.1
Eclipse Che 7.45.0
Major Enhancements
Che administrators can specify a header message on User Dasboard visible to every user
It's now possible to customize Che User Dashboard, Che users landing page, to show a message that has been setup by the administrator. The message will be visible to every user that will have access to Che User Dashboard.
Major Bug Fixes
N/A
Plugins Updates
N/A
Eclipse Che 7.44.0
Major Enhancements
Che-Theia Plugins view support for DevWorkspace based workspaces
Che-Theia now supports plugins management from the built-in Plugin View for DevWorkspace based workspaces as well.
Support for devfile v2 parents
The Devfile v2 specification introduced the concept of parent
that allow to reference an existing Devfile. Che now supports that with DevWorkspace based workspaces.
Major Bug Fixes
After upgrading to Che v7.42 it was not possible to start workspaces if the TLS ConfigMap size was bigger than 1KB
After upgrading to Che v7.42, workspaces startup failed if the TLS bundle ConfigMap size was > 1KB. To address that HTTP2 had to be disabled in the che-server to Kubernetes API.
Fix the restart of che-code based workspaces
Workspaces that use che-code as an editor failed to restart or start (if stopped). This has been fixed in this release.
Plugins Updates
Upgrade Language Support for Apache Camel by Red Hat VS Code extension to v0.1.5