Che 7.10.0 Release

[nickboldt]

List of pending issues / PRs

• (add blockers here)

Release status

In parallel, the following releases can be done:

• che-theia,
• che-machine-exec,
• che-devfile registry, then che-plugin-registry (once che-theia and machine-exec are done)
• che-parent, then che-docs, then che as Release Candidate for QE

Then in series:

• che-parent, then che-docs, then che as Release
• che-operator, then chectl

• che-theia (d0e00c5d07ec0c95a17da51a5b744934d7c4d1f8)
• che-machine-exec
• che-plugin-registry (depends on che-theia, che-machine-exec)
• che-devfile-registry
• che-parent
• che-docs (depends on parent)
• che (depends on docs and parent)
• che-operator (depends on all of the above)
  • Kubernetes community operator PR Update eclipse-che operator for kubernetes to release 7.10.0 operator-framework/community-operators#1342
  • OpenShift community operator PR Update eclipse-che operator for openshift to release 7.10.0 operator-framework/community-operators#1341
• chectl (depends on all of the above)
• complete current milestone
  • move incomplete deferred issues to backlog
  • move incomplete WIP issues to next milestone
  • close completed issues
  • close milestone

Owner	Process	Script	CI	Artifact(s)
@azatsarynnyy	che-theia	MANUAL	centos	quay.io/eclipse/che-theia
@nickboldt	che-machine-exec	make-release.sh	centos	quay.io/eclipse/che-machine-exec
@nickboldt	che-devfile-registry	make-release.sh	centos	quay.io/eclipse/che-devfile-registry
@nickboldt / @ericwill	che-plugin-registry	make-release.sh	centos	quay.io/eclipse/che-plugin-registry
@vparfonov / @mkuznyetsov	che-parent	MANUAL	centos	che-parent, che.depmgt
@vparfonov / @mkuznyetsov	che-docs	MANUAL	centos	che-docs
@vparfonov / @mkuznyetsov	che	MANUAL	centos	che.core, quay.io/eclipse/che-server
@tolusha	che-operator	make-release.sh	?	quay.io/eclipse/che-operator
@tolusha	chectl	make-release.sh	travis	chectl releases

[nickboldt]

che-theia, machine-exec, and registries are done.

Waiting on parent, docs, and server to go to RC next. @vparfonov please update this issue when you're in RC and again when RC has passed QE & release is done.

[vparfonov]

RC images updated and ready for testing

[dmytro-ndp]

Che QE team is preparing Jenkins CI jobs to test provided Eclipse Che 7.10.RC #16323

[dmytro-ndp]

Current result against Multiuser Eclipse Che 7.10.0.RC without TLS support which was installed using chectl/0.0.20200311-next.938b592 and che-operator:next installer:

1. Java selenium E2E tests passed on minishift 3.11 https://ci.centos.org/view/Devtools/job/devtools-che-rc-multiuser-integration-tests/25/
2. OS OAuth tests passed on minishift 3.11 https://ci.centos.org/view/Devtools/job/devtools-che-rc-ocp-oauth-test/26/
3. Rolling update tests passed on minishift 3.11 https://ci.centos.org/view/Devtools/job/devtools-che-rc-rolling-strategy-test/26/
4. Happy path tests, Git SSH flow tests, Vert.x, Java Maven and Python devfile tests passed on minikube 1.1.1 https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che-regular-tests/view/pre-release/job/MultiUser-Che-release-check-e2e-tests-against-k8s/40/

At the same time installation of Single User Eclipse Che 7.10.0 RC with TLS support using helm installer on minikube had failed #16338
Actually we are investigating the problem.

[dmytro-ndp]

@vparfonov: there are 7.11.0 tags in "Release preparation" commit. Shouldn't it be 7.10.0?
There is also empty tag in address of image quay.io/eclipse/che-endpoint-watcher:

[vparfonov]

fixed

[dmytro-ndp]

@vparfonov: it seems there is improper version of Eclipse Che in quay.io//eclipse/che-server:rc
SHA256 2e74e658fa4e image - 7.9.1-SNAPSHOT:

[dmytro-ndp]

@vparfonov: we checked Eclipse Che RC installation twice - there is "7.10.0-SNAPSHOT" label in quay.io//eclipse/che-server:rc SHA256 2e74e658fa4e image

[dmytro-ndp]

An issue "Make embedded OAuth authentication model default for both singe and multiuser che" has been checked successfully.

[dmytro-ndp]

Vert.x, Java Maven and Python devfile tests passed against Single User Eclipse Che 7.10.0.RC with TLS mode being installed using helm on minikube 1.1.1: https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che-regular-tests/view/pre-release/job/Single-Che-pre-release-check-test-all-devfiles-against-K8S/30/

[dmytro-ndp]

Git SSH Flow tests have passed against Single User Eclipse Che 7.10.0.RC with TLS mode being installed using helm on minikube 1.1.1 https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Single-Che-pre-release-check-Git-SSH-flow-test-against-K8S/2/

[dmytro-ndp]

@vparfonov , @nickboldt, @ibuziuk : no blockers found during pre-release testing of Eclipse Che 7.10.0.RC, which included:

• quay.io/eclipse/che-server:rc
• quay.io/eclipse/che-keycloak:rc
• quay.io/eclipse/che-theia:7.10.0
• quay.io/eclipse/che-theia-endpoint-runtime-binary:7.10.0
• quay.io/eclipse/che-devfile-registry:7.10.0
• quay.io/eclipse/che-plugin-registry:7.10.0
• quay.io/eclipse/che-plugin-artifacts-broker:v3.1.1
• chectl:next
• che-operator:nightly
• centos/postgresql-96-centos7:9.6

If there is nothing else to check, you can release provided release candidate.

[dmytro-ndp]

I would only suggest to express somewhere in documentation, that Eclipse Che 7.10.0 is now being installed with TLS enabled by default, and that the next workaround is required to install it on minikube with custom helm chart (-t chectl option):

we need to put https://raw.githubusercontent.com/che-incubator/chectl/master/installers/cert-manager.yml into the che/installers directory

Otherwise, user will encounter an error described here in issue.

[vparfonov]

Maven artifacts 7.10.0 ready link
Docker images available link

[tolusha]

che-operator, chectl 7.10.0 have been released.

[ibuziuk]

@nickboldt I guess this one can be closed, right?

[nickboldt]

Dude. If you see an issue is done, just close it.