-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins ver. 1.615
msbuild-plugin 1.24
in the msbuild system config section where you specify the msbuild installations, the "Path to MSBuild" textbox expects a directory (eg C:\windows\Microsoft.NET\Framework\v4.0.30319). if you specify the full path to msbuild.exe (eg C:\windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe) it shows a warning:
C:\windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe is not a directory on the Jenkins master (but perhaps it exists on some slaves)
however, if you omit the \msbuild.exe suffix, then builds fail with the following error:
'C:\windows\Microsoft.NET\Framework\v4.0.30319' is not recognized as an internal or external command,
operable program or batch file.
so, either:
- the config dialog should allow (and require) the \msbuild.exe suffix, or
- the build executor should append the \msbuild.exe suffix.
- is duplicated by
-
JENKINS-30489 msbuild configuration need full path with including msbuild.exe but website shows warning
- Resolved
-
JENKINS-27181 Property validators in configuration verify directory exists when parameter is asking for an executable.
- Closed
-
JENKINS-29651 Misleading warning
- Closed
-
JENKINS-34784 Path to exe needs to be the exe itself
- Closed
-
JENKINS-26221 Jenkins -> Configure System is showing a warning regarding MSBuild Configuration
- Closed