How do I perform analysis manually on Sonar Qube?

Asked 2 years ago, Updated 2 years ago, 46 views

I put Sonar Qube in my local environment and analyzed the project (larvel), but I couldn't find a way to do a second analysis (manual) although it was analyzed when I created the project.

Is there any other way to manually perform the second analysis on Sonar Qube except for the one introduced in CI?

I thought it would be good to hit the following with a terminal.
I don't know where to find the ProjectKey, password, and settings.

I installed SonarQube on Homebrew.

 sudo/Users/dddd/Downloads/sonar-scanner-macosx/bin/sonar-scanner 
- Dsonar.projectKey=XXXX
- Dsonar.sources=.  
- Dsonar.host.url=http://localhost:9000 - Dsonar.login=ffb3b2f45fbbfe24f
INFO: -------------------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: --------------------------------------------------------------------------------
INFO: Total time: 1.263s
INFO: Final Memory: 5M/24M
INFO: --------------------------------------------------------------------------------
ERROR:Error during SonarScanner execution
ERROR: Not authorized. Analyzing this project requirements authentication. Please provide a user token in sonar.login or other credentials in sonar.login and sonar.password.
ERROR: 
ERROR—Re-run SonarScanner using the -X switch to enable full debug logging.
%brew install sonar-scanner
Updating Homebrew...
==>Auto-updated Homebrew!
Updated 2taps (homebrew/core and homebrew/services).
==>New Formulae
aligner doc8 influxdb-cli notcurses pari-elldata pyoxidizer wildmidi
apt docuum joplin-clients-3 pari-galdata python-launcher xauth
aws-vault fanylicensefinder onedrive pari-galpol rsc_2faxel
bash_unit Firefoxpwa
...abbreviated
Removing: /Users/napmo/Library/Logs/Homebrew/sonarqube...(64B)
==>Upgrading 1 dependent:
sonarqube 9.0.0.45539 - > 9.0.1.46107
==>Upgrading sonarqube
  9.0.0.45539 - > 9.0.1.46107 

sonarqube: The x86_64 architecture is required for this software.
Error: sonarqube: Unsatisfied requirement failed this build.
==>Checking for dependents of upgraded formula...
==>No broken dependents found!

Enter a description of the image here

php laravel sonarqube

2022-09-30 19:12

1 Answers

It is recommended that you read the home document first.

If you refer to it,

ProjectKey Name of the project that will be displayed on the web interface.

Name of the project to be displayed in the web interface.
It can be analyzed on a project-by-project basis, and it should be OK if you include the name of the project you created.

sonar.login
The authentication token or login of a SonarQube user with Execute Analysis permission on the project.

ID of the web login user with the authentication token or permission to parse the project
To create an authentication token, see here.

sonar.password
If you're using an authentication token, leave this blank. If you're using a login, this is the password that goes with your sonar.login username.

empty if authentication token is used.
If you want to use a web login user, the password for that login

If you issue a token, you can first analyze it without the need for a password.


2022-09-30 19:12

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.