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

Path to exe needs to be the exe itself

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • fxcop-runner-plugin, msbuild-plugin
    • None
    • MSBuild Plugin 1.25
      FxCop Runner plugin 1.1

      I have MSBuild and FxCop installed on Jenkins Master (in fact only have a master so far), so the .exe-files are present.
      In the general configuration of MSBuild Plugin you have to specify the path to the MSBuild.exe.

      • If you specify just the path, no warning is shown (as the path is present on the Jenkins Master), but the build fails (as MSBuild.exe is not appended to the path).
      • If you specify the .exe itself, a warning is shown (see attached screenshot), even though the file is present. The build succeeds.

      The same goes for the FxCopCmd.exe.

      Expected behaviour: As it would influence present installtions otherwise, I suggest to change the label to "Full path to MSBuild.exe" (and ...FxCopCmd.exe) and let the warning check for the full path instead for a directory.

        1. path_to_exe1.png
          path_to_exe1.png
          103 kB
        2. path_to_exe2.png
          path_to_exe2.png
          87 kB

          [JENKINS-34784] Path to exe needs to be the exe itself

          Peter Andrews added a comment - - edited

          I would increase the priority or classification of this as it will simply stop new users (such as myself) from getting the plugin to work at all. Since 'path to MSBuild' is ambiguous as to whether it is the folder or the .exe probably a fair number of people put the path the .exe., ignore the warning and everything works. However if you put the put directory only and then the build fails, it is seriously confusing for the warning saying the path should be to a directory as it is telling you not to do exactly what is necessary to get it to work.

          Peter Andrews added a comment - - edited I would increase the priority or classification of this as it will simply stop new users (such as myself) from getting the plugin to work at all. Since 'path to MSBuild' is ambiguous as to whether it is the folder or the .exe probably a fair number of people put the path the .exe., ignore the warning and everything works. However if you put the put directory only and then the build fails, it is seriously confusing for the warning saying the path should be to a directory as it is telling you not to do exactly what is necessary to get it to work.

            marshall777 Lionel Cabasson
            robert_l Robert Lieske
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: