From 0e370a5694ff1892498c4ae39828d60e2ec02997 Mon Sep 17 00:00:00 2001 From: Suruchi Date: Mon, 9 Mar 2026 21:41:36 +0530 Subject: [PATCH 1/7] Rename sonarcloud.yml to sonarcloud.yml.old --- .github/workflows/{sonarcloud.yml => sonarcloud.yml.old} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/workflows/{sonarcloud.yml => sonarcloud.yml.old} (100%) diff --git a/.github/workflows/sonarcloud.yml b/.github/workflows/sonarcloud.yml.old similarity index 100% rename from .github/workflows/sonarcloud.yml rename to .github/workflows/sonarcloud.yml.old From 2adc2c47ac440c54d991991e1d37904d05bff97c Mon Sep 17 00:00:00 2001 From: Suruchi Date: Mon, 9 Mar 2026 22:06:13 +0530 Subject: [PATCH 2/7] Create sonarqube.yml --- .github/workflows/sonarqube.yml | 66 +++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 .github/workflows/sonarqube.yml diff --git a/.github/workflows/sonarqube.yml b/.github/workflows/sonarqube.yml new file mode 100644 index 000000000..6e3af7f14 --- /dev/null +++ b/.github/workflows/sonarqube.yml @@ -0,0 +1,66 @@ +# This workflow uses actions that are not certified by GitHub. +# They are provided by a third-party and are governed by +# separate terms of service, privacy policy, and support +# documentation. + +# This workflow helps you trigger a SonarQube analysis of your code and populates +# GitHub Code Scanning alerts with the vulnerabilities found. +# (this feature is available starting from SonarQube 9.7, Developer Edition and above) + +# 1. Make sure you add a valid GitHub configuration to your SonarQube (Administration > DevOps platforms > GitHub) + +# 2. Import your project on SonarQube +# * Add your repository as a new project by clicking "Create project" from your homepage. +# +# 3. Select GitHub Actions as your CI and follow the tutorial +# * a. Generate a new token and add it to your GitHub repository's secrets using the name SONAR_TOKEN +# (On SonarQube, click on your avatar on top-right > My account > Security or ask your administrator) +# +# * b. Copy/paste your SonarQube host URL to your GitHub repository's secrets using the name SONAR_HOST_URL +# +# * c. Copy/paste the project Key into the args parameter below +# (You'll find this information in SonarQube by following the tutorial or by clicking on Project Information at the top-right of your project's homepage) + +# Feel free to take a look at our documentation (https://docs.sonarqube.org/latest/analysis/github-integration/) +# or reach out to our community forum if you need some help (https://community.sonarsource.com/c/sq/10) + +name: SonarQube analysis + +on: + push: + branches: [ "develop-old" ] + pull_request: + branches: [ "main" ] + workflow_dispatch: + +permissions: + pull-requests: read # allows SonarQube to decorate PRs with analysis results + +jobs: + Analysis: + runs-on: ubuntu-latest + + steps: + - name: Analyze with SonarQube + + # You can pin the exact commit or the version. + # uses: SonarSource/sonarqube-scan-action@v1.1.0 + uses: SonarSource/sonarqube-scan-action@7295e71c9583053f5bf40e9d4068a0c974603ec8 + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information + SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Generate a token on SonarQube, add it to the secrets of this repo with the name SONAR_TOKEN (Settings > Secrets > Actions > add new repository secret) + SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }} # add the URL of your instance to the secrets of this repo with the name SONAR_HOST_URL (Settings > Secrets > Actions > add new repository secret) + with: + # Additional arguments for the sonarcloud scanner + args: + # Unique key of your project. You can find it in SonarQube > [my project] > Project Information (top-right menu) + # mandatory + -Dsonar.projectKey=cd3-automation-toolkit + # Comma-separated paths to directories containing main source files. + #-Dsonar.sources= # optional, default is project base directory + # When you need the analysis to take place in a directory other than the one from which it was launched + #-Dsonar.projectBaseDir= # optional, default is . + # Comma-separated paths to directories containing test source files. + #-Dsonar.tests= # optional. For more info about Code Coverage, please refer to https://docs.sonarcloud.io/enriching/test-coverage/overview/ + # Adds more detail to both client and server-side analysis logs, activating DEBUG mode for the scanner, and adding client-side environment variables and system properties to the server-side log of analysis report processing. + #-Dsonar.verbose= # optional, default is false From 2f6a3e03a2306ac12a138b599de3ff0b9ccdbf01 Mon Sep 17 00:00:00 2001 From: Suruchi Date: Mon, 9 Mar 2026 22:20:39 +0530 Subject: [PATCH 3/7] Delete .github/workflows/sonarqube.yml --- .github/workflows/sonarqube.yml | 66 --------------------------------- 1 file changed, 66 deletions(-) delete mode 100644 .github/workflows/sonarqube.yml diff --git a/.github/workflows/sonarqube.yml b/.github/workflows/sonarqube.yml deleted file mode 100644 index 6e3af7f14..000000000 --- a/.github/workflows/sonarqube.yml +++ /dev/null @@ -1,66 +0,0 @@ -# This workflow uses actions that are not certified by GitHub. -# They are provided by a third-party and are governed by -# separate terms of service, privacy policy, and support -# documentation. - -# This workflow helps you trigger a SonarQube analysis of your code and populates -# GitHub Code Scanning alerts with the vulnerabilities found. -# (this feature is available starting from SonarQube 9.7, Developer Edition and above) - -# 1. Make sure you add a valid GitHub configuration to your SonarQube (Administration > DevOps platforms > GitHub) - -# 2. Import your project on SonarQube -# * Add your repository as a new project by clicking "Create project" from your homepage. -# -# 3. Select GitHub Actions as your CI and follow the tutorial -# * a. Generate a new token and add it to your GitHub repository's secrets using the name SONAR_TOKEN -# (On SonarQube, click on your avatar on top-right > My account > Security or ask your administrator) -# -# * b. Copy/paste your SonarQube host URL to your GitHub repository's secrets using the name SONAR_HOST_URL -# -# * c. Copy/paste the project Key into the args parameter below -# (You'll find this information in SonarQube by following the tutorial or by clicking on Project Information at the top-right of your project's homepage) - -# Feel free to take a look at our documentation (https://docs.sonarqube.org/latest/analysis/github-integration/) -# or reach out to our community forum if you need some help (https://community.sonarsource.com/c/sq/10) - -name: SonarQube analysis - -on: - push: - branches: [ "develop-old" ] - pull_request: - branches: [ "main" ] - workflow_dispatch: - -permissions: - pull-requests: read # allows SonarQube to decorate PRs with analysis results - -jobs: - Analysis: - runs-on: ubuntu-latest - - steps: - - name: Analyze with SonarQube - - # You can pin the exact commit or the version. - # uses: SonarSource/sonarqube-scan-action@v1.1.0 - uses: SonarSource/sonarqube-scan-action@7295e71c9583053f5bf40e9d4068a0c974603ec8 - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information - SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Generate a token on SonarQube, add it to the secrets of this repo with the name SONAR_TOKEN (Settings > Secrets > Actions > add new repository secret) - SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }} # add the URL of your instance to the secrets of this repo with the name SONAR_HOST_URL (Settings > Secrets > Actions > add new repository secret) - with: - # Additional arguments for the sonarcloud scanner - args: - # Unique key of your project. You can find it in SonarQube > [my project] > Project Information (top-right menu) - # mandatory - -Dsonar.projectKey=cd3-automation-toolkit - # Comma-separated paths to directories containing main source files. - #-Dsonar.sources= # optional, default is project base directory - # When you need the analysis to take place in a directory other than the one from which it was launched - #-Dsonar.projectBaseDir= # optional, default is . - # Comma-separated paths to directories containing test source files. - #-Dsonar.tests= # optional. For more info about Code Coverage, please refer to https://docs.sonarcloud.io/enriching/test-coverage/overview/ - # Adds more detail to both client and server-side analysis logs, activating DEBUG mode for the scanner, and adding client-side environment variables and system properties to the server-side log of analysis report processing. - #-Dsonar.verbose= # optional, default is false From 3707a5181289d175bb7268105955904784ab30c0 Mon Sep 17 00:00:00 2001 From: Suruchi Date: Mon, 9 Mar 2026 22:20:51 +0530 Subject: [PATCH 4/7] Rename sonarcloud.yml.old to sonarcloud.yml --- .github/workflows/{sonarcloud.yml.old => sonarcloud.yml} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/workflows/{sonarcloud.yml.old => sonarcloud.yml} (100%) diff --git a/.github/workflows/sonarcloud.yml.old b/.github/workflows/sonarcloud.yml similarity index 100% rename from .github/workflows/sonarcloud.yml.old rename to .github/workflows/sonarcloud.yml From b559c1636f6243fabfe05f57f69071c424c4d4c0 Mon Sep 17 00:00:00 2001 From: Suruchi Date: Thu, 12 Mar 2026 13:07:05 +0530 Subject: [PATCH 5/7] Rename sonarcloud.yml to sonarcloud.yml.old --- .github/workflows/{sonarcloud.yml => sonarcloud.yml.old} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/workflows/{sonarcloud.yml => sonarcloud.yml.old} (100%) diff --git a/.github/workflows/sonarcloud.yml b/.github/workflows/sonarcloud.yml.old similarity index 100% rename from .github/workflows/sonarcloud.yml rename to .github/workflows/sonarcloud.yml.old From d25d39812dc2ea378121715782887afa30f3a167 Mon Sep 17 00:00:00 2001 From: Suruchi Date: Thu, 12 Mar 2026 13:22:59 +0530 Subject: [PATCH 6/7] Create sonarqube.yml --- .github/workflows/sonarqube.yml | 38 +++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 .github/workflows/sonarqube.yml diff --git a/.github/workflows/sonarqube.yml b/.github/workflows/sonarqube.yml new file mode 100644 index 000000000..9e0c72cc2 --- /dev/null +++ b/.github/workflows/sonarqube.yml @@ -0,0 +1,38 @@ +name: SonarQube Scan +on: + push: + branches: [ "develop", "main" ] + pull_request: + branches: [ "develop", "main" ] + workflow_dispatch: + +permissions: + pull-requests: read # allows SonarQube to decorate PRs with analysis results + +jobs: + Analysis: + runs-on: ubuntu-latest + steps: + - name: Checkout Repository + uses: actions/checkout@v2 + with: + # ref: ${{ github.event.pull_request.head.ref }} + # repository: ${{ github.event.pull_request.head.repo.full_name }} + fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information, if any + SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} + SONAR_HOST_URL: ${{ secrets.SONAR_HOST_URL }} # add the URL of your instance to the secrets of this repo with the name SONAR_HOST_URL (Settings > Secrets > Actions > add new repository secret) + + - name: Install Sonar Scanner + run: | + wget https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-8.0.1.6346.zip + unzip sonar-scanner-cli-*.zip + echo "$PWD/sonar-scanner-*/bin" >> $GITHUB_PATH + + - name: Run SonarQube Scan + run: | + $PWD/sonar-scanner-8.0.1.6346/bin/sonar-scanner \ + -Dsonar.projectKey=cd3-automation-toolkit \ + -Dsonar.host.url=${{ secrets.SONAR_HOST_URL }} \ + -Dsonar.token=${{ secrets.SONAR_TOKEN }} From c254c5b177c130267d29053067bc58e5fd36878f Mon Sep 17 00:00:00 2001 From: Suruchi Date: Thu, 12 Mar 2026 13:31:01 +0530 Subject: [PATCH 7/7] Update sonarqube.yml --- .github/workflows/sonarqube.yml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/.github/workflows/sonarqube.yml b/.github/workflows/sonarqube.yml index 9e0c72cc2..d405d9e8a 100644 --- a/.github/workflows/sonarqube.yml +++ b/.github/workflows/sonarqube.yml @@ -14,10 +14,9 @@ jobs: runs-on: ubuntu-latest steps: - name: Checkout Repository - uses: actions/checkout@v2 + uses: actions/checkout@v4 with: - # ref: ${{ github.event.pull_request.head.ref }} - # repository: ${{ github.event.pull_request.head.repo.full_name }} + ref: ${{ github.ref }} fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information, if any