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

"Path to Doxygen" field accepts only path without executable name

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: doxygen-plugin
    • Labels:
      None
    • Environment:
      Windows 7 Home Edition, localhost
    • Similar Issues:

      Description

      "Path to Doxygen" field accepts only path without executable name (see screenshot attached) while help section suggests full path.

        Attachments

        1. mstest.JPG
          mstest.JPG
          52 kB
        2. MSBuildPath.png
          MSBuildPath.png
          14 kB
        3. fxcop.JPG
          fxcop.JPG
          52 kB
        4. DoxygenPath.png
          DoxygenPath.png
          15 kB

          Activity

          Hide
          mvidelgauz Michael Videlgauz added a comment -

          The same happens with MSBuild configuration

          Show
          mvidelgauz Michael Videlgauz added a comment - The same happens with MSBuild configuration
          Hide
          karlthoren Karl Thorén added a comment -

          The same happens when running jenkins on linux host "/usr/bin/doxygen is not a directory on the Jenkins master (but perhaps it exists on some slaves)"

          Show
          karlthoren Karl Thorén added a comment - The same happens when running jenkins on linux host "/usr/bin/doxygen is not a directory on the Jenkins master (but perhaps it exists on some slaves)"
          Hide
          marshall777 Lionel Cabasson added a comment -

          Hello,

          I spent some time investigating this issue. It seems to me that Jenkins itself is built considering that you set a directory in the tool installation path box, that's why you get this warning.
          However, when you run a job, many plugins do not append the executable name to the path therefore you have to enter the full path to make it work.
          For instance, MSTest and FxCop runner plugin have the same issue. If you set a directory, it won't work because the exe file name is not included.
          We could correct these plugins so that they behave like they should : you would have to set the directory where the tool is installed in the administration and then, the plugin will itself append the executable name at building stage. However, we should probably keep supporting the current behavior : including the executable name in the tool configuration screen for backward compatibility.
          I don't have much experience in Jenkins plugin development and lifecycle so I'd like to have the opinion of more experienced people about what should be done here.


          Show
          marshall777 Lionel Cabasson added a comment - Hello, I spent some time investigating this issue. It seems to me that Jenkins itself is built considering that you set a directory in the tool installation path box, that's why you get this warning. However, when you run a job, many plugins do not append the executable name to the path therefore you have to enter the full path to make it work. For instance, MSTest and FxCop runner plugin have the same issue. If you set a directory, it won't work because the exe file name is not included. We could correct these plugins so that they behave like they should : you would have to set the directory where the tool is installed in the administration and then, the plugin will itself append the executable name at building stage. However, we should probably keep supporting the current behavior : including the executable name in the tool configuration screen for backward compatibility. I don't have much experience in Jenkins plugin development and lifecycle so I'd like to have the opinion of more experienced people about what should be done here.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              mvidelgauz Michael Videlgauz
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: