Che 7.13.1 release

[nickboldt]

List of pending issues / PRs

• Failed to create workspace minikube with che-operator 7.13.0 Failed to create workspace minikube with che-operator 7.13.0 #16944
• Che 7.13 release Che 7.13 release #16933
• Fix the URL syntax (for 7.13.1) PR
• (add items)

Release status

In series, the following will be released via che-release:

• che-theia, che-machine-exec, che-devfile registry,
• che-plugin-registry (once che-theia and machine-exec are done)
• che-parent, che-dashboard, che-workspace-loader, and che (server assembly)

Then manually:

• release che server in Maven Central

Then by script:

• che-operator
• generation of OperatorHub PRs
• chectl

• che-theia, che-machine-exec, che-devfile-registry, che-plugin-registry
• che-parent, che-dashboard, che-workspace-loader, che
• che-operator (depends on all of the above)
  • Update eclipse-che operator for kubernetes to release 7.13.1 operator-framework/community-operators#1768
  • Update eclipse-che operator for openshift to release 7.13.1 operator-framework/community-operators#1767
• chectl (depends on all of the above)

Owner	Process	Script	CI	Artifact(s) + Container(s)
@mkuznyetsov	che-theia	cico_release.sh	centos	eclipse/che-theia
@mkuznyetsov	che-machine-exec	cico_release.sh	centos	eclipse/che-machine-exec
@mkuznyetsov	che-plugin-registry	cico_release.sh	centos	eclipse/che-plugin-registry
@mkuznyetsov	che-devfile-registry	cico_release.sh	centos	eclipse/che-devfile-registry
@mkuznyetsov	che-parent	cico_release.sh	centos	che-parent
@mkuznyetsov	che-dashboard	cico_release.sh	centos	che-dashboard
@mkuznyetsov	che-workspace-loader	cico_release.sh	centos	che-workspace-loader
@mkuznyetsov	che	cico_release.sh	centos	che.core, eclipse/che-server, eclipse/che-endpoint-watcher, eclipse/che-keycloak, eclipse/che-postgres, eclipse/che-server, eclipse/che-e2e
@tolusha	che-operator	make-release.sh	?	eclipse/che-operator
@tolusha	chectl	make-release.sh	travis	chectl releases

[dmytro-ndp]

@nickboldt, @tolusha, @l0rd, @ibuziuk: what about including the issue "Cannot edit user account within Account Page in Dashboard " into the 7.13.1?
It could be a blocker for admins, which should change password just after installing Eclipse Che starting from 7.13.0 version (besides they could change password by using "Forgot Password" link on Login Page).

[l0rd]

@dmytro-ndp I am ok with that if @olexii4 is ok with that and if there is no risk of regression (i.e. it should have been tested properly before releasing).

[olexii4]

FYI: I have done the issue "Cannot edit user account within Account Page in Dashboard ". Minor changes.

[nickboldt]

@olexii4 I don't see a merged PR for your issue in the 7.13.x branch, nor a link to it on this issue, nor a new checkbox at the top listing the issues to be fixed in the 7.13.1 release.

Please provide the above information and links.

[olexii4]

@nickboldt My PR - Fix URL syntax

[tolusha]

chectl, che-operator are released
community operator PRs are created

[dmytro-ndp]

@tolusha: the issue #16944 hadn't been reproduced with chectl 7.13.0 on Eclipse Che 7.13.0 installed on minikube 1.1.1 by the command:

chectl server:start --k8spodreadytimeout=180000 --listr-renderer=verbose --platform=minikube --installer=operator --che-operator-cr-patch-yaml=custom-resource-patch.yaml

where:

custom-resource-patch.yaml

spec:
  server:
    cheImage: 'quay.io/eclipse/che-server'
    cheImageTag: '7.13.0'
    selfSignedCert: true
  auth:
    updateAdminPassword: false
  k8s:
    ingressDomain: '10.0.101.79.nip.io'
 

[dmytro-ndp]

@nickboldt, @olexii4: FYI: E2E AccountTest has passed on MultiUser Eclipse Che 7.13.1 without TLS support deployed to minishift 3.11, so Account Page has actually been fixed.

"Failed to create workspace minikube with che-operator" issue hasn't been reproduced on MultiUser Eclipse Che 7.13.1 with TLS support deployed to minikube 1.1.1 by using operator installer: https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/basic-MultiUser-Che-check-e2e-tests-against-k8s/1769/consoleFull

E2E JavaMaven, JavaVertx, Python devfile tests and Happy path tests have passed successfully against MultiUser Eclipse Che 7.13.1 with TLS support deployed to minikube 1.1.1 by using operator installer.

E2E JavaMaven, JavaVertx, Python devfile tests have passed successfully against SingleUser Eclipse Che 7.13.1 with TLS support deployed to minikube 1.1.1 by HELM installer.

E2E git SSH flow tests and DirectUrlFactoryWithSpecificBranchTest.factoryWithDirectUrlWithSpecificBranch have failed and should be investigated.

Update: DirectUrlFactoryWithSpecificBranchTest.factoryWithDirectUrlWithSpecificBranch test has passed been run again.

[tolusha]

All PRs are merged

[Katka92]

Devfile tests (tested on Hosted Che, verified on Che):

Java language support not working in Apache Camel K #15910
Rust error highlighting not working #15919
Apache Camel K command fails #17015
Commands do not end #17016