[JIRA] (JENKINS-57346) plugins should not rely on help from jenkins core

[jsoref+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57346  
 
 
  plugins should not rely on help from jenkins core   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Issue Type: 
 New Feature Task  
 

  
 
 
 
 

 
 
 

 
 
 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-57346) plugins should not rely on help from jenkins core

[jsoref+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57346  
 
 
  plugins should not rely on help from jenkins core   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Components: 
 active-choices-plugin, app-detector-plugin, autocomplete-parameter-plugin, bulk-builder-plugin, copyartifact-plugin, credentials-plugin, crittercism-dsym-plugin, extensible-choice-parameter-plugin, git-parameter-plugin, hidden-parameter-plugin, inflectra-spira-integration-plugin, jobgenerator-plugin, mask-passwords-plugin, metadata-plugin, p4-plugin, packageversion-plugin, perfectomobile, persistent-parameter-plugin, promoted-builds-plugin, promoted-builds-simple-plugin, random-string-parameter-plugin, run-selector-plugin, stride-notification-plugin, validating-string-parameter-plugin, worksoft-certify-process-runner-plugin  
 
 
Created: 
 2019-05-06 17:49  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/3921#issuecomment-489697493 

Of course plugins should not assume particular core resource paths exist.
 Three cases: 1. Plugins are clearly using jenkins resources: https://github.com/jenkinsci/copyartifact-plugin/search?q=%22help%2Fparameter%22_q=%22help%2Fparameter%22 

 

26  "${%Name}" field="name" help="/help/parameter/name.html">
…
31  "${%Description}" field="description" help="/help/parameter/description.html"> 

 https://github.com/jenkinsci/credentials-plugin/search?q=%22help%2Fparameter%22_q=%22help%2Fparameter%22