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

Address user confusion with veracode-scanner plugin

      Veracode maintains an official Jenkins plugin that we publish via our Help Center and will shortly be publishing to the marketplace (within the next few months). Today we get a lot of confused users asking for assistance on the open source veracode-scanner plugin via our support channels, and I note you have the opposite problem here.

      We'd like some help in reducing the confusion around which version of the plugin is supported by Veracode. I appreciate that the plugin listing page now says "not supported by Veracode" in big red letters but unfortunately this hasn't solved the problem. Is it possible to get the veracode-scanner plugin renamed? Or do you have any other creative ideas about how we might address the problem?

      Thanks for the work you've done on the plugin to date; I'm hopeful we can find a solution to this ongoing confusion.

          [JENKINS-46239] Address user confusion with veracode-scanner plugin

          Still quite confusing. veracode-scanner is the only thing you find on https://plugins.jenkins.io/. Why do I need to download the hpi file manually? Any updates, tjarrettveracode?

          Florian Wilhelm added a comment - Still quite confusing. veracode-scanner is the only thing you find on https://plugins.jenkins.io/.  Why do I need to download the hpi file manually? Any updates,  tjarrettveracode ?

          Mike Bockus added a comment -

          tjarrettveracode I think we spoke a few months back about unpublishing this plugin when the official veracode plugin is published. I don't think this open source plugin is necessary anymore since Veracode has an official supported plugin. If you would like, we could look into transitioning ownership of this plugin so the official Veracode plugin could be published and the users could just update to the supported version.  

          Mike Bockus added a comment - tjarrettveracode I think we spoke a few months back about unpublishing this plugin when the official veracode plugin is published. I don't think this open source plugin is necessary anymore since Veracode has an official supported plugin. If you would like, we could look into transitioning ownership of this plugin so the official Veracode plugin could be published and the users could just update to the supported version.  

            mbockus Mike Bockus
            tjarrettveracode Tim Jarrett
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: