-
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
Ensure release artifacts are passing some basic tests like Happy Path tests before pushing chectl release binaries #18746
Comments
@benoitf |
I am setting that one to blocker: what ever the origin of the problem, we can not just release something that is broken. |
at the moment 7.23.2 is just not working. So anyone installing che at the moment has a broken product ... |
What exactly doesn't work ?
|
So anyone who install or upgrade Che to the stable version (7.23.2 atm) can't start any workspace with plugins ... that is pretty blocker to me. It may be fixed for 7.24.0 but I think it's critical that we have a minimum of integration test for a release |
I see. We will improve our tests on che-operator side. |
I am even not sure why it is trying to reach prod preview registry :/ (I pointed the registry to another location) |
It's possible to run Happy path tests and E2E Devfile tests against already released version of Eclipse Che even now by building the next Jenkins job with proper set of parameters, if chectl binary of released version is existed https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/Che/job/e2e/job/minikube/job/basic/job/eclipse-che/ |
So that there's an owner here for the Automated Backlog, I've set Dmytro. If that's an error, please set it to someone else. |
Happy Path tests added to chectl. |
@tolusha yes |
Is your enhancement related to a problem? Please describe.
che-plugin-registry released image had invalid data in it. But all 'release process' was successful as jobs being successfully terminated.
But the resulting
latest
release was failing.We should prevent to make publicly available a release if it's not passing some basic tests.
Describe the solution you'd like
Before pushing chectl release artifacts, ensure that the tagged Che version is passing Happy Path tests.
If it does not pass, we could hold the chectl release and then end-users don't see a new version available.
Describe alternatives you've considered
Of course, each component could have its own checks as post-release check but a end-to-end check would ensure that something basic is still working.
Additional context
The text was updated successfully, but these errors were encountered: