[JIRA] (JENKINS-55632) Endless "Polling Dependency-Track for BoM processing status"

2019-01-22 Thread steve.spring...@owasp.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55632  
 
 
  Endless "Polling Dependency-Track for BoM processing status"   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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-55632) Endless "Polling Dependency-Track for BoM processing status"

2019-01-22 Thread steve.spring...@owasp.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett commented on  JENKINS-55632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Endless "Polling Dependency-Track for BoM processing status"   
 

  
 
 
 
 

 
 Default polling timeout is 5 minutes and can be configured  
 

  
 
 
 
 

 
 
 

 
 
 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-55632) Endless "Polling Dependency-Track for BoM processing status"

2019-01-16 Thread steve.spring...@owasp.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is already resolved and will be included in v2.1.0 of the plugin  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55632  
 
 
  Endless "Polling Dependency-Track for BoM processing status"   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-55632) Endless "Polling Dependency-Track for BoM processing status"

2019-01-16 Thread mark.sym...@weareact.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Symons created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55632  
 
 
  Endless "Polling Dependency-Track for BoM processing status"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Steve Springett  
 
 
Components: 
 dependency-track-plugin  
 
 
Created: 
 2019-01-17 01:17  
 
 
Environment: 
 dependency-track-plugin v2.0.2  Jenkins v2.150.1  Dependency-Track Server v3.4.0
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Symons  
 

  
 
 
 
 

 
 During times when Dependency-Track server is experiencing maxed-out CPU usage, the dependency-track-plugin (operating in synchronous mode) will endlessly poll the DT server. The Jenkins job will continue running until it is aborted, logging the following to the console: 

 
[DependencyTrack] Publishing artifact to Dependency-Track
[DependencyTrack] The artifact was successfully published
[DependencyTrack] Polling Dependency-Track for BoM processing status
[DependencyTrack] Polling Dependency-Track for BoM processing status
...
 

 The polling should have a timeout limit and then fail. This was originally reported as part of reporting high CPU usage in DT server (issue #264 and has been re-logged here in order to aid change control. Commits have already been made to address the defect. eg: Added polling timeout