Closed jachstet-sea closed 5 years ago
Thank you for reporting this. The migrator tool works (and is tested) with major releases only, such as 6.7, 7.0, and so on, not with 6.7.6. But indeed that's not so good. The latest release of 6.7.x is 6.7.7, and I believe we should make it work with that. I'll raise this issue during the week, and update this thread. In the meantime, you could try with a supported release number (6.7, 7.[0-7]).
@janosgyerik : Thanks for the information and confirmation. I will test with 7.0 today (after doing a full backup and updating to 7.0 using MySQL). I'll report back how it worked 👍
I've used Sonarqube 7.7 to do the migration and it all worked smoothly. The instane seems to be running fine on PostgreSQL now, the data on the web interface looks good from the first superficial checks. From my side, the issue can be closed since this is SOLVED for me. You might also leave it open to track the issue and for other users having the same problem. Thanks again at pointing out the version of Sonarqube version as the main problem 👍
Hi, I'm trying to migrate from MySQL (server version 5.7.25) to PostgreSQL (server version 10.7). The source and target version of SonarQube are 6.7.6.
I've created the PostgreSQL user and schema, started the target SonarQube instance, waited until it was running and then stopped it.
Then I ran the migrator and the following error was returned: "Unknown schema version; cannot match to a SonarQube release: 1838".
Any hints what I could do or how this can fixed? Thank you!