|
| 1 | +# This workflow uses actions that are not certified by GitHub. |
| 2 | +# They are provided by a third-party and are governed by |
| 3 | +# separate terms of service, privacy policy, and support |
| 4 | +# documentation. |
| 5 | + |
| 6 | +# This workflow helps you trigger a SonarCloud analysis of your code and populates |
| 7 | +# GitHub Code Scanning alerts with the vulnerabilities found. |
| 8 | +# Free for open source project. |
| 9 | + |
| 10 | +# 1. Login to SonarCloud.io using your GitHub account |
| 11 | + |
| 12 | +# 2. Import your project on SonarCloud |
| 13 | +# * Add your GitHub organization first, then add your repository as a new project. |
| 14 | +# * Please note that many languages are eligible for automatic analysis, |
| 15 | +# which means that the analysis will start automatically without the need to set up GitHub Actions. |
| 16 | +# * This behavior can be changed in Administration > Analysis Method. |
| 17 | +# |
| 18 | +# 3. Follow the SonarCloud in-product tutorial |
| 19 | +# * a. Copy/paste the Project Key and the Organization Key into the args parameter below |
| 20 | +# (You'll find this information in SonarCloud. Click on "Information" at the bottom left) |
| 21 | +# |
| 22 | +# * b. Generate a new token and add it to your Github repository's secrets using the name SONAR_TOKEN |
| 23 | +# (On SonarCloud, click on your avatar on top-right > My account > Security |
| 24 | +# or go directly to https://sonarcloud.io/account/security/) |
| 25 | + |
| 26 | +# Feel free to take a look at our documentation (https://docs.sonarcloud.io/getting-started/github/) |
| 27 | +# or reach out to our community forum if you need some help (https://community.sonarsource.com/c/help/sc/9) |
| 28 | + |
| 29 | +name: SonarCloud analysis |
| 30 | + |
| 31 | +on: |
| 32 | + push: |
| 33 | + branches: [ "master" ] |
| 34 | + pull_request: |
| 35 | + branches: [ "master" ] |
| 36 | + workflow_dispatch: |
| 37 | + |
| 38 | +permissions: |
| 39 | + pull-requests: read # allows SonarCloud to decorate PRs with analysis results |
| 40 | + |
| 41 | +jobs: |
| 42 | + sonar-check: |
| 43 | + name: Sonar Check |
| 44 | + runs-on: windows-latest # безпечно для будь-яких .NET проектів |
| 45 | + steps: |
| 46 | + - uses: actions/checkout@v4 |
| 47 | + with: { fetch-depth: 0 } |
| 48 | + |
| 49 | + - uses: actions/setup-dotnet@v4 |
| 50 | + with: |
| 51 | + dotnet-version: '8.0.x' |
| 52 | + |
| 53 | + # 1) BEGIN: SonarScanner for .NET |
| 54 | + - name: SonarScanner Begin |
| 55 | + run: | |
| 56 | + dotnet tool install --global dotnet-sonarscanner |
| 57 | + echo "$env:USERPROFILE\.dotnet\tools" >> $env:GITHUB_PATH |
| 58 | + dotnet sonarscanner begin ` |
| 59 | + /k:"ppanchen_NetSdrClient" ` |
| 60 | + /o:"ppanchen" ` |
| 61 | + /d:sonar.token="${{ secrets.SONAR_TOKEN }}" ` |
| 62 | + /d:sonar.cs.opencover.reportsPaths="**/coverage.xml" ` |
| 63 | + /d:sonar.cpd.minimumtokens=20 ` |
| 64 | + /d:sonar.exclusions=**/bin/**,**/obj/**,**/sonarcloud.yml ` |
| 65 | + /d:sonar.qualitygate.wait=true |
| 66 | + shell: pwsh |
| 67 | + # 2) BUILD & TEST |
| 68 | + - name: Restore |
| 69 | + run: dotnet restore NetSdrClient.sln |
| 70 | + - name: Build |
| 71 | + run: dotnet build NetSdrClient.sln -c Release --no-restore |
| 72 | + #- name: Tests with coverage (OpenCover) |
| 73 | + # run: | |
| 74 | + # dotnet test NetSdrClientAppTests/NetSdrClientAppTests.csproj -c Release --no-build ` |
| 75 | + # /p:CollectCoverage=true ` |
| 76 | + # /p:CoverletOutput=TestResults/coverage.xml ` |
| 77 | + # /p:CoverletOutputFormat=opencover |
| 78 | + # shell: pwsh |
| 79 | + # 3) END: SonarScanner |
| 80 | + - name: SonarScanner End |
| 81 | + run: dotnet sonarscanner end /d:sonar.token="${{ secrets.SONAR_TOKEN }}" |
| 82 | + shell: pwsh |
0 commit comments