-
Notifications
You must be signed in to change notification settings - Fork 54
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
upgrade: add appropriate warn that previous sonar will be terminated completely #429
Comments
closing as it is QA activities only |
Sonar is not started after upgrade: |
returned back to 2.1 as existing sonar has vulnerable log4j2x on board (imbedded elasticsearch) |
@okamara, let's test again |
due to the huge changes in between sonarqube versions we can't support normal upgrade. So, let's provide during the upgrade warning about destroyng previous sonar instance and data completely. And during upgrade stop sonarqube and destroy all 3 related docker volumes |
we will inform it as part of migration guide. nothing to do in bash programming for that. |
it is part of the release docs already (in draft state): https://github.com/zebrunner/community-edition/releases/tag/untagged-555e9941203286abf894
|
verified. fixed. |
CE v2.2 has sonarqube:7.9.4-community based sonar (originally on ubuntu linux).
in v2.3 we jumped to sonarqube:9.9.0-community which is on alpine.
In scope of this ticket we have to test if upgrade scenario is possible at all.
-> double check that sonar static code analysis present
git pull --recurse-submodules
./zebrunner.sh upgrade
and restart everything-> review sonarqube container logs. I suspect to see exceptions and as result inaccessible sonar
-> if sonar is available take a look to pre-upgrade analysis if it is available for user
-> double check if new analysis appear
The text was updated successfully, but these errors were encountered: