diff options
| author | G. Ann Campbell <ann.campbell@sonarsource.com> | 2018-09-27 11:01:47 -0400 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2018-10-03 09:28:21 +0200 |
| commit | d8bee945bc625291b60a411a37339450fa01a15a (patch) | |
| tree | 92c7a55ee6a117c05f1d72a813a38cc53f2f13ff /server/sonar-docs/src/pages/architecture | |
| parent | 4e20e6a9ff7014608708040b3e082011da6a3631 (diff) | |
| download | sonarqube-d8bee945bc625291b60a411a37339450fa01a15a.tar.gz sonarqube-d8bee945bc625291b60a411a37339450fa01a15a.zip | |
Revert "MMF-1458 Port SONAR-space docs to embedded docs" (#766)
This reverts commit a7893ef0a269df9bcd39e929e7851aeb6a1b8ed8.
Diffstat (limited to 'server/sonar-docs/src/pages/architecture')
| -rw-r--r-- | server/sonar-docs/src/pages/architecture/architecture-integration.md | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/server/sonar-docs/src/pages/architecture/architecture-integration.md b/server/sonar-docs/src/pages/architecture/architecture-integration.md deleted file mode 100644 index e05a454ca4c..00000000000 --- a/server/sonar-docs/src/pages/architecture/architecture-integration.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Architecture and Integration -url: /architecture/architecture-integration/ ---- -The SonarQube Platform is made of 4 components: - -1. One SonarQube Server starting 3 main processes: -a. Web Server for developers, managers to browse quality snapshots and configure the SonarQube instance -b. Search Server based on Elasticsearch to back searches from the UI -c. Compute Engine Server in charge of processing code analysis reports and saving them in the SonarQube Database -2. One SonarQube Database to store: -* the configuration of the SonarQube instance (security, plugins settings, etc.) -* the quality snapshots of projects, views, etc. -3. Multiple SonarQube Plugins installed on the server, possibly including language, SCM, integration, authentication, and governance plugins -4. One or more SonarQube Scanners running on your Build / Continuous Integration Servers to analyze projects - - -## Integration -The following schema shows how SonarQube integrates with other ALM tools and where the various components of SonarQube are used. - -1. Developers code in their IDEs and use SonarLint to run local analysis. -2. Developers push their code into their favourite SCM : git, SVN, TFVC, ... -3. The Continuous Integration Server triggers an automatic build, and the execution of the SonarQube Scanner required to run the SonarQube analysis. -4. The analysis report is sent to the SonarQube Server for processing. -5. SonarQube Server processes and stores the analysis report results in the SonarQube Database, and displays the results in the UI. -6. Developers review, comment, challenge their Issues to manage and reduce their Technical Debt through the SonarQube UI. -7. Managers receive Reports from the analysis. -Ops use APIs to automate configuration and extract data from SonarQube. -Ops use JMX to monitor SonarQube Server. - - -## About Machines and Locations -* The SonarQube Platform cannot have more than one SonarQube Server and one SonarQube Database. -* For optimal performance, each component (server, database, scanners) should be installed on a separate machine, and the server machine should be dedicated. -* SonarQube Scanners scale by adding machines. -* All machines must be time synchronized. -* The SonarQube Server and the SonarQube Database must be located in the same network -* SonarQube Scanners don't need to be on the same network as the SonarQube Server. -* There is **no communication** between **SonarQube Scanners** and the **SonarQube Database**. |