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

Upload fails when using Fortify 3.30

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • fortify360-plugin
    • Windows Server 2008
      Jenkins ver. 1.409.2
      Fortify ver. 3.30

      Hi, We have been using the Fortify360 plugin for a while, works like a charm. But we have recently upgraded to Fortify 3.30. We noticed that if 3.30 is on the system Path the plugin will look there for the 4 files it needs to do the upload (i.e. wsclient.jar,wsobjects.jar, common.jar,common13.jar). Problem is they are not there (in core/lib/) in 3.30, at least they are not named the same. So, if we leave the Version field blank in the global Jenkins config, or we enter 3.30 we get an error that the plugin can't find the .jars it needs.
      We can get around it by using 3.30 to do the scans but entering 2.65 for the Jars Path for the upload. But still seems like it should be fixed going forward.

      Here is an example of the error:
      Error uploading to F360 Server: http://ourfortifyserver/f360
      java.lang.RuntimeException: Invalid JarsPath: N:\Program Files (x86)\Fortify Software\HP Fortify v3.30\Core\lib, can't locate common.jar or common13.jar

      Let me know if you need any more info or need me to try anything. I am glad to help.

      Thanks!
      Bernie Bonn

            samngms samngms
            bbonn bbonn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: