[JIRA] (JENKINS-54441) Display class and plugin for workflow steps

[email protected] (JIRA) Mon, 05 Nov 2018 05:19:33 -0800

Title: Message Title

Craig Ringer commented on

It looks like the Descriptor abstract base that StepDescriptor extends exposes a getPlugin() method that would be ideal. AFAICS in src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/index.jelly.

I think it needs to inject getPlugin().getDisplayName() hyperlinked to its getPlugin().getUrl(), and probably the step class's getSimpleName() too.

I haven't figured out how to do that in jelly (I used JSF2 in a prior life, but I've never done jelly) and don't have a local Jenkins for testing yet. But hopefully this is a useful starting point. My wild guess is:

In the <f:ajax> block, maybe after the end of the <st:include/> block, something like

 
                                                                <j:set var="plugin" value="${descriptor.plugin}"/>
<tr>
  <td colspan="3">
    Provided by class <tt>${descriptor.simpleName}</tt>
    <j:if test="${plugin != null}">
      <j:set var="pluginUrl" value="${plugin.url}"/>
      <j:set var="pluginName" value="${plugin.displayName}"/> 
      <j:if test="${pluginUrl == null}>
        in plugin ${pluginName}.
      </j:if>
      <j:if test="${pluginUrl != null}>
        in plugin <a href="" class="code-quote" style="color: #009100">"${pluginUrl}">${pluginName}</a>.
      </j:if>
    </j:if>
  </td>
</tr>
 
                                                            

I'd love a hand as I'm a bit stuck about how to get from this to testing it and sending a pull request.

Add Comment

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54441) Display class and plugin for workflow steps

Reply via email to