Skip to content

up the date to retrigger analysis #170

up the date to retrigger analysis

up the date to retrigger analysis #170

Workflow file for this run

name: Build
on:
push:
branches:
- main
pull_request:
types: [opened, synchronize, reopened]
jobs:
build:
name: Build
runs-on: windows-latest
env:
BUILD_WRAPPER_OUT_DIR: build_wrapper_output_directory # Directory where build-wrapper output will be placed
COVERAGE_RESULTS: coverage_results # Directory where coverage results will be placed
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
- name: Set up msbuild
uses: microsoft/setup-msbuild@v1.1
- name: Setup VSTest.console.exe # Needed to run tests and generate coverage
uses: darenm/Setup-VSTest@v1.2
- name: Install sonar-scanner and build-wrapper
uses: SonarSource/sonarcloud-github-c-cpp@v2
- name: Run build-wrapper
run: |
build-wrapper-win-x86-64 --out-dir ${{ env.BUILD_WRAPPER_OUT_DIR }} msbuild sonar_scanner_example.vcxproj /t:rebuild /nodeReuse:false
- name: Build tests
run: |
msbuild test1\test1.vcxproj
msbuild test2\test2.vcxproj
- name: Run tests with coverage
run: >
vstest.console.exe test1\*\test1.dll test2\*\test2.dll
/EnableCodeCoverage
/Collect:"Code Coverage;Format=Xml"
/ResultsDirectory:"${{ env.COVERAGE_RESULTS }}"
- name: Run sonar-scanner
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
SONAR_TOKEN: ${{ secrets.SONARCLOUD_TOKEN }} # Put the name of your token here
run: >
sonar-scanner
--define sonar.cfamily.compile-commands="${{ env.BUILD_WRAPPER_OUT_DIR }}/compile_commands.json"
--define sonar.cfamily.vscoveragexml.reportsPath="${{ env.COVERAGE_RESULTS }}/*/*.xml"