-
DarkLight
Can I create a new SonarQube instance and use the existing CodeScan licence if one of my SonarQube instances was mistakenly deleted?
Yes, you can reinstall CodeScan Self-Hosted and continue to utilise your existing licence.
After you've set up the prerequisites, you can use your existing account and password to log into SonarQube. If it doesn't work, try logging in with the admin username and password.
- Login into SonarQube using below credentials:
- username: admin
- password: admin
- Go to the top right and select Administrator.
- On the right side, select General Settings.
- On the category list, select CodeScan.
- In the CodeScan licence text box, type your licence key (key is sf.licence.secured).
- Save the file.
Is it possible to scan the standard field using the Salesforce Metadata rule "Custom fields must have a description field" for Quality Profile?
According to our current CodeScan configuration, the "Custom fields must have a description field" rule of Salesforce Metadata (Beta) does not scan standard fields.
When I run a CodeScan analysis on a project, the app throws warning errors.
If this problem occurs as a result of project duplication, we propose deleting the duplicated project and re-running the analysis.
Getting an error “Salesforce\force-app\main\default\applications\Chatter_Delete_Blocker.app-meta.xml” when writing a custom SonarQube rules using the Xpath Template rule for Salesforce Metadata (sfmeta:XPathRule).
Cause: Analysis is looking for a match with a file name and the suffix entered in the field, but it is unable to find any, which is why they are receiving this error.
Solution: This is an expected behaviour as Codescan is unable to decide which rules to apply for the said files.
To remove file patterns listed for sonar.lang.patterns.xml, navigate to Project Settings > General Settings > Language.