wiki/info/landscape/building-and-deploying.md
... ...
@@ -111,9 +111,15 @@ After at most 90 days, the vault secret expire. Then, under [https://hyperspace.
111 111
Couldn't fetch secret at 'piper/PIPELINE-GROUP-5565/PIPELINE-29049/cumulus' - Error making API request
112 112
```
113 113
114
-see also [here](https://pages.github.tools.sap/SAPMobile/Documentation/Support/faq/#my-pipeline-fails-with-invalid-secret-id-or-invalid-role-id).
114
+see also [here](https://pages.github.tools.sap/SAPMobile/Documentation/Support/faq/#my-pipeline-fails-with-invalid-secret-id-or-invalid-role-id).
115 115
116
-Our points of contact for the Hyperspace / Azure Pipeline migration are Marc Bormeth (marc.bormeth@sap.com), Maurice Breit (maurice.breit@sap.com) and Philipp Resch (philipp.resch@sap.com).
116
+The build uses a SonarQube check step. For that, the [SonarQube Security Configuration](https://sonar.tools.sap/account/security) is where we create access tokens. These, in turn, have to be set in the [Vault here](https://vault.tools.sap/ui/vault/secrets/piper/kv/PIPELINE-GROUP-5565%2FPIPELINE-29049%2Fsonar-SAP-Sailing-Analytics-Sonarqube/details?namespace=ies%2Fhyperspace%2Fpipelines) as a new version in the ``token`` field, with the ``url`` field being set to ``https://sonar.tools.sap``. These tokens are good for at most one year. The error we see upon token expiry would be something like
117
+```
118
+error sonarExecuteScan - 18:56:54.249 ERROR Error during SonarScanner CLI execution
119
+info sonarExecuteScan - java.lang.IllegalStateException: Error status returned by url [https://sonar.tools.sap/api/v2/analysis/jres?os=linux&arch=x86_64]: 401
120
+```
121
+
122
+Our points of contact for the Hyperspace / Azure Pipeline migration are Marc Bormeth (marc.hertel@sap.com), Maurice Breit (maurice.breit@sap.com) and Philipp Resch (philipp.resch@sap.com), and the Slack channel ``#sap-cop-mobile-cicd``.
117 123
118 124
### Running a Build / Release / Promote Cycle
119 125