[JIRA] (JENKINS-53597) Plugins used in pipelines are not reported

[fro...@premium-minds.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Filipe Roque commented on  JENKINS-53597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugins used in pipelines are not reported   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/plugin-usage-plugin/pull/12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194079.1537100418000.10846.1573170900324%40Atlassian.JIRA.

[JIRA] (JENKINS-53597) Plugins used in pipelines are not reported

[cha...@online.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53597  
 
 
  Plugins used in pipelines are not reported   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 plugin-usage-plugin  
 
 
Created: 
 2018-09-16 12:20  
 
 
Labels: 
 pipeline  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Chad Williams  
 

  
 
 
 
 

 
 Within an environment where most jobs recently have been migrated to version controlled Jenkinsfiles, I was hoping to use this plugin for cleaning up plugins that dropped out during said migration. I'm aware that the wiki states 

Plugins used in pipeline scripts would not be listed normally as used by jobs, because they are used dynamically in Jenkinsfiles.
 However, I was under the impression that not be listed normally as used by jobs implies that they are listed as something else. The wiki should clearly state that currently, plugins used by pipeline builds are not shown _at all*. That being said, it would be be very nice to have pipelines covered such that this plugin can also be of use in modern version-controlled CI setups. I understand that dynamic plugin loading is a difficulty, analyzing past builds of every job would however already be a great step forward.