Handle post release notifications

[costin-zaharia-sonarsource]

Notifications

• Send notification to the sonar cloud team about:

  • Update: https://github.com/SonarSource/sonarcloud-core/blob/5aea36a7da4edae2de47d99495c2cdf60dff3e95/dop-translation/autoscan/dotnet/docker/build.sh#L14
  • When we create the update task of S4NET for AutoScan on SonarCloud, we should specify that the package file names are now different
  • Documentation needs to be updated: https://docs.sonarsource.com/sonarcloud/advanced-setup/ci-based-analysis/sonarscanner-for-net/ most probably it will be done by updating https://github.com/SonarSource/sonar-update-center-properties/blob/03d6bf58aa38a30565b3f01e1e30243c491b67cf/scannermsbuild.properties#L19-L26

• Send notification to the sonar qube team about:

  • Documentation needs to be updated: https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner-for-dotnet/ most probably it will be done by updating https://github.com/SonarSource/sonar-update-center-properties/blob/03d6bf58aa38a30565b3f01e1e30243c491b67cf/scannermsbuild.properties#L19-L26
  • VMS needs to be updated: https://github.com/SonarSource/vms/blob/196980595bfd072f7af74053e17ce904c4224c77/gcp/windows/vs2017-builds-tools/vs2017-build-tools.json#L56
  • Jenkins is using the scanner as well: https://github.com/SonarSource/sonar-scanner-jenkins/blob/74905c49f10c040c4ed78739c3f8950e2dd0d86c/its/src/test/java/com/sonar/it/jenkins/SonarPluginTestSuite.java#L86 (jira project can be found here: https://sonarsource.atlassian.net/jira/software/c/projects/SONARJNKNS)
  • Jenkins crawler: https://github.com/jenkins-infra/crawler/blob/master/sonarqubescannermsbuild.groovy

• Inform PMs to update:

  • https://github.com/SonarSource/sonar-update-center-properties/blob/03d6bf58aa38a30565b3f01e1e30243c491b67cf/scannermsbuild.properties#L19-L26

• Sonar documentation needs to be updated as well:

  • Check the code owners: https://github.com/SonarSource/sonar-documentations/blob/main/.github/CODEOWNERS
  • Usage: https://github.com/SonarSource/sonar-documentations/blob/ef3c39eb8cb2c6d9cc73c52183da74c0355da9b3/__mocks__/__data__/SonarScanner/SonarScanner.mock.json#L16
  • Usage: https://github.com/SonarSource/sonar-documentations/blob/121a7832382029b1a687c122695fce7830b5182b/src/components/SonarScanner/__tests__/__snapshots__/SonarScanner.test.tsx.snap#L190
  • Send an email to the documentation team with the changes for https://docs.sonarsource.com/sonarqube/9.8/analyzing-source-code/scanners/sonarscanner-for-dotnet/#:~:text=name%20for%20now.-,The%20SonarScanner%20for%20.,SonarScanner%20for%20

• and also to change the mention of “Scanner for MSBuild 4.6” in https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/jenkins-extension-sonarqube/

[antonioaversa]

Draft PRs to test S4NET 6.0 in other repos:

• https://github.com/SonarSource/sonar-dotnet-autoscan/pull/628
• https://github.com/SonarSource/sonar-security/pull/4701
• Update ITs to always use the latest version of the Scanner for .NET sonar-dotnet#8439

The PRs are mainly to test behavior after the release of S4NET 6.0 and may be closed once we run the following three sub-tasks:

• Update sonar-dotnet to use the latest version of the orchestrator and scanner
• Update sonar-security to use the latest version of the orchestrator and scanner
• Update sonar-dotnet-autoscan to use the latest version of the orchestrator and scanner