Che Platform Sprint 200

[skabashnyuk]

Timeframe

Apr. 14 - May 4

Team

Name
@sparkoo
@metlos
@mshaposhnik
@xbaran4
@skabashnyuk

Holidays / events:

• Apr. 23 Hack 'n' Hustle
• May 3,4 Ukraine Holidays

CRW releases

CRW 2.5 is based on Eclipse Che 7.20.x
CRW 2.6 is based on Eclipse Che 7.24.x
CRW 2.7 is based on Eclipse Che 7.26.x
CRW 2.8 is based on Eclipse Che 7.28.x
CRW 2.9 is based on Eclipse Che 7.30.x

---

GitLab

• Gitlab private repo support using OAuth 2 flow | Gitlab private repo support using OAuth 2 flow  #19171

Bitbucket

• Improve workflow when a user denies Bitbucket access for Che | Improve workflow when user denies Bitbucket access for Che #19274
• The default devfile is resolved from private bitbucket repo after access token is revoked | The default devfile is resolved from private bitbucket repo after access token is revoked #19273

Devworkspaces

• [devworkspace-che] Support custom certificates for gateway and workspace endpoints [devworkspace-che] Support custom certificates for gateway and workspace endpoints #19394
• Define CheCluster v2alpha1 | Define CheCluster v2alpha1 #19449

Authentication and authorization in Eclipse Che

• [che-auth] - new auth on Openshift with OAuth and devworkspaces | [che-auth] - new auth on Openshift with OAuth and devworkspaces #19576

Docs/Tehnocal debt/bugs

• [doc] Not able to configure "per user" project strategy because users didn't had enough privileges. | [doc] Not able to configure "per user" project strategy because users didn't had enough privileges. #19572
• factory resolver misses volume component from devfile 2.0 | factory resolver misses volume component from devfile 2.0 #19563

Unplanned

• che-server failed to start che-server failed to start #19599
• Failing unit test KubernetesNamespaceFactoryTest when building Che serve Failing unit test KubernetesNamespaceFactoryTest when building Che server #19641
• Vulnerability found in che-server image Vulnerability found in che-server image #19650
• Secret and deployment name normalization required when using SCM username in PersonalAccessToken management Secret and deployment name normalization required when using SCM username in PersonalAccessToken management #19700