bbonn created JENKINS-12695:
-------------------------------
Summary: Upload fails when using Fortify 3.30
Key: JENKINS-12695
URL: https://issues.jenkins-ci.org/browse/JENKINS-12695
Project: Jenkins
Issue Type: Bug
Components: fortify360
Environment: Windows Server 2008
Jenkins ver. 1.409.2
Fortify ver. 3.30
Reporter: bbonn
Assignee: samngms
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
