-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Che 7.9.2 Release #16229
Comments
The patch for about dialog already included in 7.9.1 |
slip to 7.11:
|
@nickboldt: can we include fix of import in Che with TLS in this release: eclipse-che/che-theia#672 ? |
waiting for QE to proceed with RC testing |
@davidfestal, @tolusha: installation of Multiuse User Eclipse Che 7.9.2.RC on minikube 1.1.1 using chectl:next and che-operator:nightly had failed:
Could you, please, say which version of chectl and che-operator we should use to check installation of Eclipse Che 7.9.2.RC? |
Have you tried using the 7.9.1 version of operator/chectl? Was there anything useful in the logs to explain WHY it timed out? |
I can try with che-operator:7.9.1.
|
Sure but you also can't check it with the 7.10 or 7.11 operator either :D |
For now you can use quay.io/dfestal/che-operator:fix-devfile-registry-public-url But I assume that if you need to continuously test the bits of the |
That is why we need to have che-operator:7.9.2 image, and chectl:7.9.2 which will be used later to build crwctl for CRW 2.1.0. |
Are you suggesting that we should revise the release process so that @tolusha will release the operator and chectl BEFORE che server 7.9.2 is live? Would that work? |
Yes - it would be perfect! |
while David provided newer che-operator, here is how you could build newest chectl: git clone https://github.com/che-incubator/chectl use compiled binaries from "bin" directory |
we don't need the che-server maven artifacts to release che-operator and chectl |
It's okay to have hardcoded |
@mkuznyetsov: we can't build chectl from https://github.com/che-incubator/chectl/commits/7.9.x on CRW CCI because there is too old node version:
Also I don't see significant changes compare to chectl:7.9.1 in https://github.com/che-incubator/chectl/commits/7.9.x. So, IMHO, we can use chectl:7.9.1 this time. |
@davidfestal, @nickboldt: Eclipse Che 7.9.2.RC installation failed because the was We need to backport commit which disabled installation of Che in TLS mode in pre-release testing scripts into 7.9.x branch. |
@mkuznyetsov, @nickboldt, @davidfestal:
Current result against Multiuser Eclipse Che 7.9.2.RC without TLS support:
Also, @davidfestal reported that he had successfully tested fixes related to che-operator:7.9.x on a disconnected OS 4.3 cluster, installed with the restricted environment procedure, with proxies + TLS + selfsigned certificates enabled. Result was a successfully started Java Gradle workspace, with working basic services like terminal, JDTLS, outlines, and commands. Next tests are in-progress:
|
Happy path tests, Vert.x, Java Maven and Python devfile tests against Multiuser Eclipse Che 7.9.2.RC on minikube 1.1.1 have passed successfully: 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/50/ |
GitHub integration tests have passed as well. |
It was decided to create Eclipse Che 9.7.2.RC2 with the next fix inside:
|
Current result against Multiuser Eclipse Che 7.9.2.RC2 without TLS support:
Version number is been displayed correctly in Dashboard: If there is nothing else needed to test, Eclipse Che 7.9.2.RC2 can be release. |
Che 7.9.2 server and docs are live in quay and maven central. ~ 11pm EST Mar 20. |
|
List of pending issues / PRs
Release status
In parallel, the following releases can be done:
Then in series:
quay.io/eclipse/che-theia
quay.io/eclipse/che-machine-exec
quay.io/eclipse/che-devfile-registry
quay.io/eclipse/che-plugin-registry
quay.io/eclipse/che-server
quay.io/eclipse/che-operator
The text was updated successfully, but these errors were encountered: