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

Whitesource-plugin changed product name

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: whitesource-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.150.3
      WhiteSource plugin 19.1.1
      Pipelines scripted
    • Similar Issues:

      Description

      Hi,

      I use whitesource plugin within scripted Pipelines at groovy:

      def scanStep() {
          script.echo " *** start WhiteSource scan ***"
          script.echo "productName: ${this.productName}"
         script.echo "productVersion: ${this.productVersion}"
         script.echo "includes: ${this.includes}"
         script.echo "excluded: ${this.excludes}"

         script.whitesource jobApiToken: this.jobApiToken,
                       jobCheckPolicies: 'global', jobForceUpdate: 'global',
                       libIncludes: this.includes,
                       libExcludes: this.excludes,
                       product: this.productName,
                       productVersion: this.productVersion
           script.echo "*** stop WhiteSource scan ***"
      }

      Execution Console output:
      07:31:52 *** start WhiteSource scan **[Pipeline] echo*07:31:52 productName: node-js-sample[Pipeline] echo*07:31:52* productVersion: 1.1.1-devel[Pipeline] echo*07:31:52* includes: */.js[Pipeline] echo*07:31:52* excluded: [Pipeline] whitesource*07:31:52* Updating White Source.07:31:52 Collecting OSS usage information*07:31:52* Starting generic job on /myworkspace*07:31:53* Job finished.07:31:53 WhiteSource Service URL:07:31:53 Checking policies*07:31:52* Scanning folder ojects_MD_jpl-sample-npm_develop*07:31:53* Found 322 dependencies matching include / exclude pattern in folder.07:32:55 Generating policy check report*07:32:55* Some dependencies violate open source policies, however all were force updated to organization inventory.07:32:55 Sending to White Source*07:32:57* WhiteSource update results: 07:32:57 WhiteSource organization: *****07:32:57 0 Newly created projects:07:32:57 07:32:57 1 existing projects were updated:07:32:57 develop - 1.1.1-devel*07:32:57* WhiteSource Support Token: ****
      Summary page WhiteSource published:

      Policy Check Summary

      Policy Violations Found

      Build Name - develop
      Build Number - 212
      Report creation time - 2019-03-14 07:32:55
       
      No new projects found
       
      Existing Projects(found 1 existing projects)

      develop - 1.1.1-devel

      It looks like product parameter to plugin is ignored and plugin used branch name or folder name instead. It should be product name as provided by product parameter.
      It behaves the same for npm and maven projects and WhiteSource reports at SaaS service are not categorized correctly.

       

        Attachments

          Activity

          Hide
          slawiek Slawomir Wieczorkowski added a comment -

          It may be related to fact that MultiBranch pipeline type is used.

          Anyway I think it should be possibility to keep product name as provided

          and project version should be always product - productVersion.

           

          Show
          slawiek Slawomir Wieczorkowski added a comment - It may be related to fact that MultiBranch pipeline type is used. Anyway I think it should be possibility to keep product name as provided and project version should be always product - productVersion.  

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            slawiek Slawomir Wieczorkowski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: