Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-76149

SonarScanner for MSBuild fails to detect 'dotnet' if its PATH is set dynamically at job execution time instead of being loaded from the agent's startup environment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • sonar-plugin
    • None
    • Jenkins version: 2.440.1
      SonarQube Scanner for Jenkins version: 2.17.2
      Jenkins agent OS: Ubuntu 22.04

      The SonarScanner for MSBuild integration in a Jenkins pipeline fails to locate the dotnet executable when its path is added to the PATH environment variable dynamically during the build (e.g. via Exported variables). The execution only succeeds if the dotnet path is already present in the PATH variable loaded from the Jenkins agent's startup environment (e.g. via .bashrc).

            sonarteam Sonar Team
            nsalvi_afea Nicolò Salvi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: