[JIRA] (JENKINS-56584) Allow to enforce quality gate at WhiteSource step

2019-03-15 Thread slawomir.wieczorkow...@finastra.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Slawomir Wieczorkowski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56584  
 
 
  Allow to enforce quality gate at WhiteSource step   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 whitesource-plugin  
 
 
Created: 
 2019-03-15 14:51  
 
 
Environment: 
 Jenkins ver. 2.150.3  WhiteSource plugin 19.1.1  Pipelines scripted  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Slawomir Wieczorkowski  
 

  
 
 
 
 

 
 Currenly WhiteSource Plugin could be defined to fail job only globally at Jenkins Global Setting section. This functionality should be allowed at whitesource step as parameter to call within pipeline.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
   

[JIRA] (JENKINS-56576) Whitesource-plugin changed product name

2019-03-15 Thread slawomir.wieczorkow...@finastra.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Slawomir Wieczorkowski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56576  
 
 
  Whitesource-plugin changed product name   
 

  
 
 
 
 

 
Change By: 
 Slawomir Wieczorkowski  
 
 
Attachment: 
 jenkins_output.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56576) Whitesource-plugin changed product name

2019-03-15 Thread slawomir.wieczorkow...@finastra.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Slawomir Wieczorkowski commented on  JENKINS-56576  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitesource-plugin changed product name   
 

  
 
 
 
 

 
 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.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56576) Whitesource-plugin changed product name

2019-03-15 Thread slawomir.wieczorkow...@finastra.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Slawomir Wieczorkowski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56576  
 
 
  Whitesource-plugin changed product name   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 whitesource-plugin  
 
 
Created: 
 2019-03-15 08:30  
 
 
Environment: 
 Jenkins ver. 2.150.3  WhiteSource plugin 19.1.1  Pipelines scripted  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Slawomir Wieczorkowski  
 

  
 
 
 
 

 
 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