Skip to main content

SonarQube Installation locally on Windows

Download the SonarQube community edition from https://www.sonarsource.com/products/sonarqube/downloads/

update the path in 

sonarqube-8.9.10.61524\conf\wrapper.conf

edit below path

wrapper.java.command=C:\Program Files\Java\jdk-11\bin\java

Goto the below path

\sonarqube-8.9.10.61524\bin\windows-x86-64\

and run startsonar.bat

there are four steps:

1 create a project and generate the user token and generate login token and copy it

2 donwload the sonarscanner and set the path

3 go to the project path and run the below command

sonar-scanner.bat -D"sonar.projectKey=DEMO" -D"sonar.sources=." -D"sonar.host.url=http://localhost:9000" -D"sonar.login=XXXXX"

4 go the sonarqube dashboard and refresh it the dashboard


Any 3rd party tool is required for generating the code coverage and inject that along with sonarqube, 

sonarqube should be feed with code coverage tool in order to see the code coverage results in sonarqube dashboard. 



Comments

Post a Comment

Popular posts from this blog

Jenkins for salesforce on RHEL OS or CentOS and configuring jenkins slave

To find the version  cat /etc/os-release sudo su - yum install jyava-11-openjdk-devel curl --silent --location http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo | sudo tee /etc/yum.repos.d/jenkins.repo sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key sudo yum install jenkins -y sudo systemctl enable jenkins sudo systemctl start jenkins systemctl status jenkins sudo firewall-cmd --permanent --zone=public --add-port=8080/tcp sudo firewall-cmd --reload =================================================== Create a another instance for slave connect the vm using pem file and  cd ~/.ssh ssh-keygen -t rsa -C "The access key for Jenkins slaves" cat id_rsa.pub > ~/.ssh/authorized_keys cat id_rsa Add the SSH Private Key to Jenkins Credentials Go to jenkins dashboard –> credentials –> Global credentials –> add credentials Create a Slave in jenkins CONFIGURE AGENT -> LAUNCH METHOD -> Manually trusted key verification strategy - > SAVE. If Manua...
Post a Comment
Read more

Reducing Manual Tasks in Salesforce DevOps

  🚩Focus: Automating the Deletion of Old Flow Versions ❓One of the most frequently asked questions I get as a DevOps Consultant is: “How can we reduce manual tasks during deployments?” A common manual task is deleting outdated Flow versions in Salesforce. Here’s why automating this step is valuable: 🚨 Why Automate This? Deleting old Flow versions is a best practice that helps in several ways: Improves overall performance Reduces clutter in the environment Makes the system easier to manage, especially during continuous development and iteration How to Automate Flow Deletion Deleting old Flow versions is fairly simple in itself, but doing it manually across multiple orgs during forward or backward promotions can become a tedious and error-prone process. 🚩Here are a few ways to automate it: 1. Using Salesforce Inspector Reloaded or Other Tools Supporting Tooling API You can run a query to fetch obsolete Flow versions and delete them using tools that support the Tooling API. 2. Usin...
Post a Comment
Read more