Hi, Due to relatively low demand and to reduce our maintenance overhead, we will be switching off the Eclipse SonarQube server (https://sonar.eclipse.org/) on September 1st, 2020.
We are currently running an hopelessly outdated version (4.5.7), since an upgrade was blocked by dropped support for older MySQL DB versions and a constant lack of time. ~60 projects have set up a project on our SonarQube server over the years. Only a couple of these projects seem to still actively use it. How do we know that? A few weeks ago, we've retired an old database server and moved it's DBs to a new server, including the SonarQube DB. In this process, the database URL changed, which (unintentionally) broke the SonarQube setup on all Jenkins instances. So far, only 5 projects (of ~60) filed a bug report about this. Another reason to get rid of our SonarQube server is the availability of SonarCloud.io (the cloud based version of SonarQube by SonarSource). It provides easy integration with GitHub and still allows to connect non-GitHub projects. We will support projects to migrate to SonarCloud.io. Please open a Bugzilla issue (Product: Community, Component: Sonar) for this. See also: https://wiki.eclipse.org/Jenkins#How_can_SonarCloud_be_integrated_into_a_Jiro_JIPP.3F Switching of the SonarQube server will be tracked via: https://bugs.eclipse.org/bugs/show_bug.cgi?id=564871. Please let me know, if you have any questions or concern. Regards, Fred -- Frederic Gurr Release Engineer | Eclipse Foundation Europe GmbH Annastr. 46, D-64673 Zwingenberg Handelsregister: Darmstadt HRB 92821 Managing Directors: Ralph Mueller, Mike Milinkovich, Gaël Blondelle _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
