Newer versions of SonarQube have stopped supporting MariaDB and you may need to switch to MySQL instead. While I’d rather use MariaDB, I understand that it is not within the supported matrix. Therefore I am documenting the steps here. The steps are focused on RHEL 7 (they probably would work on Centos 7 as well, but I did not test it).
Before start with this process, shutdown your SonarQube instance as well as any other analysis that may access the database.
The first step is to use mysqldump to create a backup of your MariaDB database:
mysqldump sonar > sonar.sql
After the backup is complete, shutdown and disable your MariaDB instance:
systemctl stop mariadb ; systemctl disable mariadb
Then install MySQL 5.7 from Software Collections. The process is documented on this page. These steps are for 5.6, however, you can just replace 56 with 57 in all the steps and the result is the same.
With the new MySQL 5.7 installed and running, create the database:
In the MySQL sheel recreate the database with the same credentials and permissions as the old one:
CREATE USER '[old username]'@'localhost' IDENTIFIED BY '[old password]';
GRANT ALL PRIVILEGES ON *.* TO '[old username]'@'localhost' WITH GRANT OPTION;
CREATE USER '[old username]'@'%' IDENTIFIED BY '[old password]';
GRANT ALL PRIVILEGES ON *.* TO '[old username]'@'%' WITH GRANT OPTION;
Then you can recover the backup into the new MySQL 5.7 instance:
mysqldump sonar < sonar.sql
Now you can go to your SonarQube server and start it.
For the most part of my professional life I worked as an IT Specialist in Brazil. An IT specialist is a professional that designs, develops, employs or maintains information technology systems. It is a pretty broad term that may encompass several different different job roles (from database administrators to software engineers to production support analysts). In my case, I was engaged with 2 primary activities: software development and application architecture.
All of that changed 3 months when I left my IT Specialist job in Brazil and moved to Czech Republic to work as a Software Quality Engineer (aka Quality Engineer) for Middleware Messaging products. Since then, a few friends had come to me to ask: a) what I am doing, b) what exactly a Quality Engineer does and c) do you write code. With that said, I think I have answered question ‘a’. Since question ‘a’ is already answered, let me explain what is a Software Quality Engineer (SQE) and it does.
A SQE is a specialized type of engineer that works on all phases of development to design, develop and execute tools, process and strategies to ensure that software products meet or exceed desired levels of quality (with quality being defined as the degree of excellence of an item or product).
A SQE usually:
- Design, develop and maintain tools to perform automated testing
- Develop and maintain automated test cases
- Elaborate and implement Continuous Integration (CI) and Continuous Delivery (CD) strategies including its infrastructure and support tools
- Help to investigate and verify security issues
- Elaborate and execute test plans
- Define and implement software quality metrics and design, develop and maintain tools to collect them
- Review product documentation
Whether an SQE writes code depends on what type of products it works with. For example, in my case I work with tools for messaging and enterprise application integration, therefore I tend to write code quite frequently, as most of these products are used by software developers, IT specialists and IT architects to integrate disparate systems.