{"id":97620,"date":"2020-10-19T20:42:40","date_gmt":"2020-10-19T18:42:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-my-vnedrili-sonarqube-i-osoznali-ego-bolshoj-potenczial"},"modified":"2020-10-19T20:42:40","modified_gmt":"2020-10-19T18:42:40","slug":"kak-my-vnedrili-sonarqube-i-osoznali-ego-bolshoj-potenczial","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/kak-my-vnedrili-sonarqube-i-osoznali-ego-bolshoj-potenczial","title":{"rendered":"How we implemented SonarQube and recognized its great potential.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"How<\/p>\n

<\/p>\n

We want to share our experience in implementing the SonarQube platform for continuous analysis and measurement of code quality into the existing development processes of the DPO system (an addition to the depository and clearing accounting system 'Alameda') of the National Settlement Depository. <\/p>\n

<\/a><\/noindex><\/p>\n

The National Settlement Depository (part of the Moscow Exchange Group) is one of the key companies in the financial infrastructure, storing and accounting for securities of Russian and foreign issuers worth over 50 trillion rubles. The increasing volume of operations conducted by the system, along with the continuous expansion of functionality, demands the maintenance of high quality source code. One of the tools to achieve this goal is the SonarQube static analyzer. In this article, we will describe the successful experience of seamlessly integrating the SonarQube static analyzer into the existing development processes of our department. <\/p>\n

<\/p>\n

About the Department<\/h3>\n

<\/p>\n

Our competencies include the following modules: client payments to the NSD, electronic document management, processing trade repository messages (registering off-exchange transactions), channels for electronic interaction between clients and the NSD, and much more. Overall, we have a substantial workload concerning the technical aspects of operational activities. We work based on requests. The requests of the operators are processed by analysts: they gather client requirements and present us with their vision of how it should be reflected in the software. Next follows the standard scheme: code development \u2013 testing \u2013 pilot operation \u2013 delivery of code to the production environment to the end client. <\/p>\n

<\/p>\n

Why SonarQube?<\/h3>\n

<\/p>\n

This is our department's first experience implementing a platform for code quality control \u2013 previously, we did this manually, only conducting code reviews. However, the growing workload necessitates the automation of this process. Additionally, there are inexperienced staff members on the team who are not entirely familiar with internal development regulations and are prone to making more mistakes. To ensure code quality, it was decided to implement a static code analyzer. Since SonarQube was already used in some systems of NRD, the choice was straightforward. Previously, colleagues from other divisions used it to analyze microservice code in the 'Alameda' system (NRD's proprietary depository-clearing accounting system), in CFT (an information system for managing accounting, balance sheets, and preparing mandatory and internal reports), and in several other systems. For experiments, we decided to start with the free version of SonarQube. So, let\u2019s move on to our case.<\/p>\n

<\/p>\n

Implementation process<\/h2>\n

<\/p>\n

We have<\/strong>:<\/p>\n

<\/p>\n