Skip to content

Eclipse Che 7.68.0
Compare
Choose a tag to compare
@l0rd l0rd released this 29 Jun 10:59
· 197 commits to main since this release
7.68.0
0ae2398

Major Enhancements

Simpler workspaces URLs Backported to 7.67

Starting from this release, workspaces URLs don't include random characters anymore but use username, workspace name, endpoint name or port. For example if user john creates a quarkus-todo workspace that exposes a backend endpoint using my-che-instance.com, then:

  • The VS Code URL will be https://my-che-instance.com/john/quarkus-todo/3100
  • The endpoint application preview will be https://john-quarkus-todo-backend.my-che-instance.com/

Users can configure Git Personal Access Tokens in their Preferences

With the new tab named Personal Access Token in Users Preferences, developers can manage GitHub, GitLab, Bitbucket and Azure DevOps personal access tokens using the UI. Before that developers had to manually create a Kubernetes secret.

image

Allow admins to specify workspaces gateway and project-clone containers Backported to 7.67

Sections gatewayContainer and projectCloneContainer have been added in CheCluster .spec.devEnvironments to allow adminstrators to specify the containers that will host the workspaces reverse proxy (gateway) and the container that clones the remote git repositories respectively:

spec:
  devEnvironments:
    gatewayContainer:
        (...container settings...)
    projectCloneContainer:
        (...container settings...)

In particular it is now possible to unset the CPU limits for those containers. For example this is how it can be done for the gateway container:

spec: 
  devEnvironments: 
    gatewayContainer: 
      resources: 
        limits: 
          cpu: "0"

Allow users to configure VS Code workspaces with a .code-workspaces file Backported to 7.67

.code-workspace files allow developers to configure their VS Code workspace. Starting from this release developers can specify the ..code-workspace file in its project using the environment variable VSCODE_DEFAULT_WORKSPACE in the devfile:

schemaVersion: 2.2.0
(...)
components:
- name: dev-tools
  container:
    (...)
    env:
    - name: VSCODE_DEFAULT_WORKSPACE
      value: "/projects/che-demo-app/che-demo.code-workspace"

Major Bug Fixes

The Eclipse Che configuration of the default VS Code extensions is ignored

A bug affecting Eclipse Che from release v7.58 prevented an administrator to specify a default list of IDE plugins, in particular VS Code extensions. This got fixed an it's now possible to specify the VS Code extensions that will be automatically included in Dev Spaces using this field devEnvironments.defaultPlugins in CheCluster Custom Resource.

Devfile component with deployByDefault set to false should be ignored at workspace startup

Workspaces startup was failing when a Kubernetes component was using the uri field, no matter the value of deployByDefault. Some of the samples in OpenShift Developer Console were failing to load in Eclipse Che because of this problem. Now Kubernetes components that have the field deployByDefault set to false are ignored at workspace startup.

Assets 2
Loading