Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Before closing TAMAYA-12 I had a look at Apache's SonarCube and could not find our projects there.
Task is to find out why we lost them and if so, to readd them.
Target environment:
-https://builds.apache.org/analysis- deprecated! Use SonarCloud instead!
Target links
- https://sonarcloud.io/dashboard?id=incubator-tamaya_180410
- apache_incubator-tamaya = project-key
- apache = organization key
- generate badge in README.md of each project
- https://sonarcloud.io/dashboard?id=apache_incubator-tamaya-extensions
- apache_incubator-tamaya-extensions = project-key
- https://sonarcloud.io/dashboard?id=apache_incubator-tamaya-sandbox
- apache_incubator-tamaya-sandbox = project-key
- In order to spot problems with the build file you need to check:
- https://travis-ci.org/apache/incubator-tamaya-sandbox/requests for each repo/Travis integration
Links
- https://docs.travis-ci.com/user/sonarcloud/ - Integration with Travis/Sonarcloud
- does not work as it needs a proper login to encryp tokens ....
- Run manual analysis: TOKENGOESHERE = manually generated after logging in to sonarcloud.io
mvn sonar:sonar \ -Dsonar.projectKey=apache_incubator-tamaya \ -Dsonar.organization=apache \ -Dsonar.host.url=https://sonarcloud.io \ -Dsonar.login=TOKENGOESHERE goes through mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install sonar:sonar \ -Dsonar.projectKey=apache_incubator-tamaya \ -Dsonar.organization=apache \ -Dsonar.host.url=https://sonarcloud.io \ -Dsonar.login=TOKENGOESHERE
- Settings in Travis itself - thanks acoburn
The second approach involves adjusting the settings in the Travis-CI web
interface: https://travis-ci.org/apache/incubator-tamaya/settings
Under the "Environment Variables" section, you'd need to add an entry with
the Name set to SONAR_TOKEN and the Value set to the value of the token
from Sonarcloud. Make sure that "Display value in build log" is set to
"false".
Attachments
Issue Links
- causes
-
TAMAYA-394 Fix existing sonar warnings after integrating with SonarCloud
- Open
- is caused by
-
TAMAYA-11 Integrate tools for code analysis in Tamaya
- Closed
- links to
(5 links to)
There are no Sub-Tasks for this issue.