Database used source path as mysql and target path as postgresql
Portfolio won’t available for projects post migration from sonarqube 6.5 to 8.0 - Need solution to address portfolio issue as part of migration
Have done migration to new version of sonarqube 8.0 so far. Detail steps which i followed given below.
1.Download and unzip the SonarQube versions in a fresh directory as per migration path given above , let’s say $NEW_SONARQUBE_HOME
2.Used plugins that are compatible with version of SonarQube.
3.Update the contents of sonar.properties and wrapper.conf files (in $NEW_SONARQUBE_HOME/conf) with the settings of the related files in the $OLD_SONARQUBE_HOME/conf directory (web server URL, database, ldap settings, etc.).
4.Stop old SonarQube Server
5.Start new SonarQube Server by deleting data & tmp folder
6.Browse to http://yourSonarQubeServerURL/setup and follow the setup instructions
7.Reanalyze your projects to get fresh data
Database used source path as mysql and target path as postgresql
Portfolio won’t available for projects post migration from sonarqube 6.5 to 8.0 - Need solution to address portfolio issue as part of migration and provide detailed steps to fix this. Please note i have tried reindexing the ES but could not achieve.
Have done migration to new version of sonarqube 8.0 so far. Detail steps which i followed given below.
1.Download and unzip the SonarQube versions in a fresh directory as per migration path given above , let’s say $NEW_SONARQUBE_HOME
2.Used plugins that are compatible with version of SonarQube.
3.Update the contents of sonar.properties and wrapper.conf files (in $NEW_SONARQUBE_HOME/conf) with the settings of the related files in the $OLD_SONARQUBE_HOME/conf directory (web server URL, database, ldap settings, etc.).
4.Stop old SonarQube Server
5.Start new SonarQube Server by deleting data & tmp folder
6.Browse to http://SonarQubeServerURL/setup and follow the setup instructions
7.Reanalyze your projects to get fresh data
Please find my comments for above questions
No Enterprise Edition used. We are using Community Edition.
As part of upgrade, we migrated from MYSQL to Postgresql 10.x .
We have re-analyzed the projects at Database but portfolio summary is not available for migrated projects only.
Yes, I am expecting steps to get portfolios for projects post migration with community Edition
Please provide detail steps to address this issue.
Community Edition doesn’t offer portfolios, so I’m not sure what it is that’s not working for you. In case you’re talking about the Projects page, then it could be a corrupted Elasticsearch index. For that, you should try:
shut the server down
delete $SONARQUBE-HOME/data/es6
restart the server
If it’s something else, then it’s likely provided by a 3rd-party plugin & you should contact the maintainers of that plugin.
I have already done the steps given above and still getting projects portfolio error as “The main branch of this project is empty” post migration from SQ 6.5 to 8.0.
Followed below steps post migration from 6.7.7 LTS to 7.9.4 LTS, 7.9.4 LTS to 8.0 with community Edition.
1). shutdown the sonarqube server post migration
2). deleted $SONARQUBE-HOME/data/es6 & $SONARQUBE-HOME/tmp/
3).restarted the sonarqube server
PFA for your reference and Please note that this issue is exists during the migration from 6.7.7 LTS to 7.9.4 LTS and 7.9.4 LTS to 8.0.
Could you please give solution to address this issue during migration
Followed below steps for upgrade.
1.Download sonarqube and unzip the SonarQube versions in a fresh directory as per migration path given in above topics.
2.Used plugins that are compatible with version of SonarQube.
3.Update the contents of sonar.properties with MySQL
4.Stop SonarQube Server
5.Start SonarQube Server by deleting data & tmp folder
6.Browse to http://hostname:port/setup and click on Upgrade
7.Post Upgrade sonarqube server started and then login with credentials then screen appear as below.