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

Property validators in configuration verify directory exists when parameter is asking for an executable.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When modifying the Jenkins configuration the validators that run to check if the value you typed in exists evaluate to invalid when you specify an executable instead of the directory it resides in. If you only specify the directory to appease the validator, the plugin does not work as it seems to expect a path all the way down to the .exe.

      I've noticed this on both mstest and msbuild plugins, but it may affect the configuration of others as well.

      I am attaching screenshots of the configuration page to show the "valid"(doesn't work) and the "invalid"(does work) state of the page.

      When only specifying the directory, the resulting command for msbuild is this:

      Executing the command cmd.exe /C " C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ /p:VisualStudioVersion=12.0 /t:build /p:Configuration=Release
      'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\' is not recognized as an internal or external command, operable program or batch file.

        Attachments

        1. msbuildInvalid.PNG
          msbuildInvalid.PNG
          21 kB
        2. msbuildValid.PNG
          msbuildValid.PNG
          15 kB
        3. mstestInvalid.PNG
          mstestInvalid.PNG
          23 kB
        4. mstestValid.PNG
          mstestValid.PNG
          17 kB

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              Assignee:
              marshall777 Lionel Cabasson
              Reporter:
              dineenr Bobby Dineen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: