Skip to end of metadata
Go to start of metadata

Plugin Information

View Fortify on Demand Uploader on the plugin site for more information.

This plugin provides a post build action for submitting code to Fortify on Demand for security assessment. 


Fortify on Demand is the cloud-based application security testing service. This plugin enables Fortify on Demand customers to upload code for Static Application Security Testing (SAST) directly from Jenkins.

This plugin features:

  • Fortify on Demand static security assessment for each build triggered by Jenkins
  • Task to poll for results and mark the build as ‘Unstable’ if it does not meet the organization's security policy

This plugin requires a Fortify on Demand account. For more details and to request a free trial, go to


1. Generate API Key

Jenkins connects to your Fortify on Demand tenant via the Fortify on Demand API. To create an API key, login to the Fortify on Demand Portal and select Administration->Settings->API. Then, add a new API key with role "Start Scans." Make a note of the API Key and the secret code that is displayed.

2. Install Plugin

From the Jenkins Dashboard, go to Manage Jenkins-> Manage Plugins. In the Available tab and search for “Fortify on Demand Uploader”. Select the plugin and the click on Download and install after restart.

3. Global Configuration

From the Jenkins Dashboard, go to Manage Jenkins-> Configure System. Under Fortify on Demand enter the API Key and secret code from Step 1 above. In advanced settings enter the URL that you use for accessing Fortify on Demand. The Test Connection button may be used to validate your settings. If your Jenkins server requires a proxy for web access configure it under Plugin Manager -> Advanced -> HTTP Proxy Configuration.

4. Project Configuration

For each project that requires a Fortify on Demand Security assessment and click Configure. Add Build Step Fortify on Demand Upload and configure the parameters following the help text provided.

The project will now be configured to run a Fortify on Demand assessment for each build triggered by Jenkins.

5. View Results

If the upload is successful the results will be available in the Fortify on Demand portal.

Fortify on Demand allows organizations to specify an application security policy based on a combination of the applications risk rating and the criticality of any vulnerabilities found. If the application meets the organization's security policy the build will be marked as stable. If it does not it will be marked as unstable.

6. Troubleshooting

Diagnostic information for each build is available from Console Output.

Additional Considerations For Maven Users

For the most complete assessment of your application it is important to ensure all dependencies for deployment are satisfied. Maven provides a simple means of outputting these libraries by the maven-dependency-plugin. The section, <excludeGroupIds> may be used to ensure test framework code, for example, is not included.

Example POM Section:

POM Plugins Entry



Known Limitations

  • The plugin requires that Jenkins is running on Java 1.8
  • The 2.0.9 (Obsolete) plugin version is slow to populate the pull down menu's in Redhat 7 machines.  Please wait a minute or two and the first field should populate.
  • The plugin requires an internet connection to Fortify on Demand and a valid Fortify on Demand license.

Change Log

Version 3.0.1 (10-9-2017)

Upgrade Note: - please be aware that builds will need to be reconfigured with the BSI Url/Token.

  • Scans are now configured with the BSI Url/Token from the Static Scan Setup page of the release to be scanned in the Fortify on Demand Portal.
Version 2.0.6 (1-6-2017)
  • Fixed bug that causes plugin to crash configuration pages when incomplete information was saved.
Version 2.0 (4-28-2016)
  • Fixed bug when that causes plugin to crash when particular proxy configurations cause authentication to fail.
  • Finalized update to FoD API V3
Version 1.10 (4-28-2016)

*Bug Fix:* This release addresses a rare issue in which release information may not be retrieved for certain applications.

  • Corrected encoding issue for application names which can prevent release information calls from working properly
  • Additional validation for global polling interval
  • Removed unsupported language level settings for .NET and Java
Version 1.09 (4-25-2016)
  • Code changes to resolve distributed Jenkins defect (credit to Ruud Senden)
  • Minor language support changes in preparation for potential new mobile assessment types
Version 1.08 (4-15-2016)
  • Added support for Jenkins proxy configuration
  • Added connection configuration test button that validates reachability of the portal and tests credentials
Version 1.07 (4-6-2016)
  • Added option to include/exclude identified third-party libraries from analysis results
  • Changed order, and description, of advanced options for consistency with the Fortify on Demand portal
  • Polling for results is no longer default. Applications set to poll will reflect your organization's security policy in Jenkins via build stability.
  • Minor branding changes
Version 1.06

*Bug Fix:* This release addresses a bug where the Assessment Type may not correctly set under certain conditions

  • Assessment Type no longer has a suggested default selection; the user must choose the proper type for enabled entitlement
  • Added .NET as a supported language to Sonatype help text
Version 1.05

Upgrade Note: - please ensure you reconfigure any existing builds so that the filer filter may be set by the plugin; this functionality has changed with this version.

  • Added support for all language/assessment types except MBS and C/C++, which require pre-processing with Fortify SCA prior to submission to Fortify on Demand
  • Files selected for upload are automatically set based on language type and Fortify on Demand requirements; users may opt to package all files, including extraneous types like media, under advanced options. Using the automated default is highly encouraged
  • The result report link added with the Detailed Reports option now refers to the Overview page in the Customer Portal
Version 1.04

Upgrade Note: - please ensure you reconfigure any existing builds so that Assessment Type may be set by the plugin as this field is new with this version.

  • Static-related assessment types may be selected at upload, defaults to "Static Assessment"
  • API calls for information lookup are now more resilient with retries, and have additional logging of any issues, e.g. lack of assessment entitlement
Version 1.03
  • Star rating and total issue count display in the standard log results
  • Detailed build log table output includes a deep link to the FoD customer portal for the application release, issue counts by criticality, and Fortify on Demand star rating
  • Minor code cleanup for readability
Version 1.02
  • Minor branding changes
  • Updated UI API token secret validation due to changed 5.0 portal format
Version 1.01
  • Initial release

Feedback Welcome

This plugin is maintained by the Fortify on Demand team. If you have any problems, questions, or enhancement requests or would like to contribute to the code please let us know via GitHub Issues.


  1. The 2.0.4 version of this plugin will dump the stack trace when you try to save the Jenkins main Configuration screen, or the individual Jenkins Job Configuration screen.  While the changes to the Jenkins main Configuration screen do appear to be saved prior to the stack dump, the individual job changes are not saved.  The Asset Type, Release Name, and Entitlement Id text field pull down menu's are blank even after setting up the plugin and testing the connection to HP.

    The notes say this requires Java 1.7, however this is an older version of Java and the plugin needs to be updated to Java 1.8.

    The last working version of this plugin we've been able to use is the 1.10 release.  I've tested a 2.0.5 snapshot fix and that is a little better (it doesn't stack dump on the Jenkins main Configuration screen), it doesn't fix the stack dump on the individual Jenkins Job Configuration screen.  All in all, 2.0.4 is not something I would use and need significant improvement.  Ticket JENKINS-27498, and 25102 have been opened with CloudBees and HP FoD Support.  CloudBees has been very responsive and helpful.  HP has been virtually silent for three weeks.

    CloudBees did provide this snapshot$fortify-on-demand-uploader/ for testing which works better, but still has problems with saving the individual job configurations.

    Stack tracejavax.servlet.ServletException:java.lang.Error:Failedtoinstantiateclassorg.jenkinsci.plugins.fodupload.FodUploaderPluginfromblktokxyzkdtnhgnsbdfblktok12blktokxyzkdtnhgnsbd">Stack tracejavax.servlet.ServletException: java.lang.Error: Failed to instantiate class org.jenkinsci.plugins.fodupload.FodUploaderPlugin from
    Unknown macro: {"assessmentTypeId"}

    at org.kohsuke.stapler.Stapler.tryInvoke(
    at org.kohsuke.stapler.Stapler.invoke(
    at org.kohsuke.stapler.MetaClass$5.doDispatch(
    at org.kohsuke.stapler.NameBasedDispatcher.dispatch(
    at org.kohsuke.stapler.Stapler.tryInvoke(
    at org.kohsuke.stapler.Stapler.invoke(
    at org.kohsuke.stapler.Stapler.invoke(
    at org.kohsuke.stapler.Stapler.service(
    at javax.servlet.http.HttpServlet.service(
    at org.eclipse.jetty.servlet.ServletHolder.handle(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at hudson.util.PluginServletFilter$1.doFilter(
    at hudson.util.PluginServletFilter$1.doFilter(
    at hudson.plugins.greenballs.GreenBallFilter.doFilter(
    at hudson.util.PluginServletFilter$1.doFilter(
    at jenkins.metrics.impl.MetricsFilter.doFilter(
    at hudson.util.PluginServletFilter$1.doFilter(
    at hudson.util.PluginServletFilter.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(
    at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(
    at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(
    at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at org.kohsuke.stapler.compression.CompressionFilter.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at hudson.util.CharacterEncodingFilter.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
    at org.eclipse.jetty.servlet.ServletHandler.doHandle(
    at org.eclipse.jetty.server.handler.ScopedHandler.handle(
    at org.eclipse.jetty.server.session.SessionHandler.doHandle(
    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
    at org.eclipse.jetty.servlet.ServletHandler.doScope(
    at org.eclipse.jetty.server.session.SessionHandler.doScope(
    at org.eclipse.jetty.server.handler.ContextHandler.doScope(
    at org.eclipse.jetty.server.handler.ScopedHandler.handle(
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
    at org.eclipse.jetty.server.Server.handle(
    at org.eclipse.jetty.server.HttpChannel.handle(
    at org.eclipse.jetty.server.HttpConnection.onFillable(
    at winstone.BoundedExecutorService$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
    Caused by: java.lang.Error: Failed to instantiate class org.jenkinsci.plugins.fodupload.FodUploaderPlugin from

    Unknown macro: {"assessmentTypeId"}

    at hudson.model.Descriptor.newInstance(
    at hudson.model.Descriptor.newInstancesFromHeteroList(
    at hudson.model.Descriptor.newInstancesFromHeteroList(
    at hudson.util.DescribableList.rebuildHetero(
    at hudson.model.Project.submit(
    at hudson.model.Job.doConfigSubmit(
    at hudson.model.AbstractProject.doConfigSubmit(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.kohsuke.stapler.Function$InstanceFunction.invoke(
    at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(
    at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(
    at org.kohsuke.stapler.Function.bindAndInvoke(
    at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(
    at org.kohsuke.stapler.MetaClass$1.doDispatch(
    at org.kohsuke.stapler.NameBasedDispatcher.dispatch(
    at org.kohsuke.stapler.Stapler.tryInvoke(
    ... 64 more
    Caused by: java.lang.IllegalArgumentException: Failed to instantiate class org.jenkinsci.plugins.fodupload.FodUploaderPlugin from

    Unknown macro: {"assessmentTypeId"}

    at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(
    at org.kohsuke.stapler.RequestImpl.bindJSON(
    at org.kohsuke.stapler.RequestImpl.bindJSON(
    at hudson.model.Descriptor.newInstance(
    ... 82 more
    Caused by: java.lang.NumberFormatException: For input string: ""
    at java.lang.NumberFormatException.forInputString(
    at java.lang.Integer.parseInt(
    at java.lang.Integer.parseInt(
    at org.jenkinsci.plugins.fodupload.models.JobConfigModel.<init>(
    at org.jenkinsci.plugins.fodupload.FodUploaderPlugin.<init>(
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
    at java.lang.reflect.Constructor.newInstance(
    at org.kohsuke.stapler.RequestImpl.invokeConstructor(
    at org.kohsuke.stapler.RequestImpl.instantiate(
    at org.kohsuke.stapler.RequestImpl.access$200(
    at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(
    ... 85 more

  2. The 2.0.5 version of this plugin is slightly better in that it no longer does a Java stack trace dump when saving the http://<Jenkins_url>/configure screen, but it still does a Java stack trace dump when trying to save any Jenkins Job that tries to use the Post-Build FoD plugin.  The issue appears to be that three of the data field pull down menu's (Asset Type, Release Name, and Entitlement Id ) are left blank (after the plugin is installed and the "test" button has been clicked on).  There is no documentation on how to configure these fields so they remain empty and the plugin does not check for this (obvious) condition.  There is nothing that says these fields are required either.

    Since the pull down menu's are configured by the initial test connection to HP, I don't understand why these fields are empty.  If there is something that needs to be configured by the Jenkins Admin, that needs to be documented in this Wiki page, but there is nothing specified here, or in the Jenkins system configuration screen.

  3. The HP ticket 25102 says there is a 2.0.6 version under development and provided the URL to get the hpi file.  When I tried to download all I got was a 404 error message. 

  4. I've been playing with the 2.0.6 release and happened to get interrupted for about 10 minutes. Durring this time, the Release Name field populated itself with the "baseline" value when the Application Name was set to "1Dispatch". In looking at the org.jenkinsci.plugins.fodupload.FodUploaderPlugin.xml configuration file this value seems correct (i.e. they have the same <applicationId> value "78460"). However ten minutes for a field to populate is really far to long for practical usage.

    The Assessment Type, and Entitlement Id fields populated with values of "0" for both fields, however when looking at the org.jenkinsci.plugins.fodupload.FodUploaderPlugin.xml configuration file it appears there should be several choice which are not being displayed in the pull down lists. Clearly this plugin is not ready for prime time at all.

    It appears the org.jenkinsci.plugins.fodupload.FodUploaderPlugin.xml file is being read, but is not being processed correctly for the display fields. This renders the plugin useless.

  5. Okay, this is weird. I've done nothing on the test machine (no builds, not activities of any kind) and went to lunch. When I came back and opened the Jenkins task configuration screen, the Assessment Type and Entitlement Id fields now have values populated into the fields and the pull down menus have choices shown where before they were empty. The test machine is hidden from other developers and I'm the only one with access so I'm sure no one has been messing with the system.

    I've no idea why this should suddenly populate the data fields or why the pull down menu's seem to be working all of the sudden. (Witchcraft I say, get the torches and pitchforks ready). :) Does the Development team have any idea why this should suddenly populate these values after several hours of nothing happening?

  6. plugins are not supporting javascript projects upload.

    Unable to select language level.This is blocking our automation works

  7. Hi,

    I have successfully done plugin installation but couldn't see the Plugin info in Manage Jenkins→ Configure System(Configure Global settings and paths).

    Please what would be the problem for not displaying/appearing in the tab: Configure System of Jenkins web UI. Due to this I couldn't load/select/choose the plugin during Jenkins Maven build Job creation.

    Here is the method used for installing Fortify On Demand plugin.

    Advanced installation

    The Update Center only allows the installation of the most recently released version of a plugin. In cases where an older release of the plugin is desired, a Jenkins administrator can download an older .hpi archive and manually install that on the Jenkins master.

    From the web UI

    Assuming a .hpi file has been downloaded, a logged-in Jenkins administrator may upload the file from within the web UI:

    1. Navigate to the Manage Jenkins > Manage Plugins page in the web UI.

    2. Click on the Advanced tab.

    3. Choose the .hpi file under the Upload Plugin section.

    4. Upload the plugin file.


    1. Does the plugin show up under your installed plugins section?

      1. Yes Matt, plugin "Fortify on Demand Uploader Plugin" is under Installed Plugins section.

        Here are the details about plugin:

        Fortify on Demand Uploader Plugin (fortify-on-demand-uploader): 3.0.6

        Note: We are using Jenkins version: 1.650

        Issue here is that I couldn't see Fortify on Demand Uploader Plugin information under Configure System. Ideally the plugin should be dispayed but here it is not like that.

        Manage Jenkins

        Configure global settings and paths.