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

msbuild configuration need full path with including msbuild.exe but website shows warning

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • msbuild-plugin
    • windows machine with build tools VS2013 or VS2015

      When you setup msbuild path on "Manage Jenkins" -> "Configure System" with only path.
      The build will fail, because msbuild.exe is missing in cmd line.
      When we configure it with complete path, like on screenshot, build works, but the configuration website shows a warning, that we must specify a directory instead of a file.

      This behavior was on all jenkins server which we use.

      It seems to be not happen for .NET 4.0 msbuild in the Windows folder!

        1. 2015-09-16 14_32_50-Configure System [Jenkins].png
          2015-09-16 14_32_50-Configure System [Jenkins].png
          12 kB

          [JENKINS-30489] msbuild configuration need full path with including msbuild.exe but website shows warning

          Hans van Luttikhuizen added a comment -

          I've also encountered this problem. The configuration doesn't clearly specify whether it requires the folder or the executable. It gives a warning when the executable is given, even though it is actually what is required.

          Please either fix the warning or the expected behaviour and better communicate what information exactly is required.

          Hans van Luttikhuizen added a comment - I've also encountered this problem. The configuration doesn't clearly specify whether it requires the folder or the executable. It gives a warning when the executable is given, even though it is actually what is required. Please either fix the warning or the expected behaviour and better communicate what information exactly is required.

          Ronny Borchert added a comment -

          I update today to jenkins 2.17 and latest msbuild 2.16 version. Same error only little text change:
          C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)

          Ronny Borchert added a comment - I update today to jenkins 2.17 and latest msbuild 2.16 version. Same error only little text change: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)

          Ronny Borchert added a comment -

          update to latest version brings only different text, but warning persists:
          C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)

          Ronny Borchert added a comment - update to latest version brings only different text, but warning persists: C:\Program Files (x86)\MSBuild\14.0\Bin\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some agents)

          Lionel Cabasson added a comment -

          This is the correct behavior : you should set the directory containing msbuild.exe and not the full path. That's why you get this warning.
          In the previous versions however, setting the path without "msbuild.exe" was not working. This is not the case anymore. For backward compatibility purpose, your current setting still works but is incorrect. You should set the directory which make your job run the same way it does now and remove the warning.

          Lionel Cabasson added a comment - This is the correct behavior : you should set the directory containing msbuild.exe and not the full path. That's why you get this warning. In the previous versions however, setting the path without "msbuild.exe" was not working. This is not the case anymore. For backward compatibility purpose, your current setting still works but is incorrect. You should set the directory which make your job run the same way it does now and remove the warning.

            marshall777 Lionel Cabasson
            arbeita Ronny Borchert
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: