JenkinsIcon indicating the project type

Jenkins

Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9467

jenkins-plugin-info macro assumes subversion when it can't find github

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: prereq-buildstep
    • Labels:
      None
    • Environment:
      jenkins wiki
    • Similar Issues:
    • URL:

      Description

      the jenkins-plugin-info macro used to display the plug-in information defaults to java.net subversion structure when it does not find expected Github information. This results in wrong link for certain plug-ins

      I suggest the logic is changed so if the macro dos not understand the scm information it just displays the 3 scm urls from the pom file or nothing at all
      See URL for example

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          dankirkd Daniel Kirkdorffer added a comment -

          The macro documentation is poor. When I look for it in the Confluence Macro Browser it doesn't indicate any of the additional attributes that are valid for it as described at https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins.

          Anyway, this problem affects the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin as well. The code is hosted at Google Code, and evidently that's not supported by the macro, so even though we use Mercurial, it shows "Subversion" as the SCM.

          Perhaps the macro can have another attribute to indicate the SCM, and one to provide a path?

          Show
          dankirkd Daniel Kirkdorffer added a comment - The macro documentation is poor. When I look for it in the Confluence Macro Browser it doesn't indicate any of the additional attributes that are valid for it as described at https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins . Anyway, this problem affects the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin as well. The code is hosted at Google Code, and evidently that's not supported by the macro, so even though we use Mercurial, it shows "Subversion" as the SCM. Perhaps the macro can have another attribute to indicate the SCM, and one to provide a path?
          Hide
          Permalink
          varsketiz Titas Norkūnas added a comment -

          If it is not github, it should just take the <url> tag from POM and not try to guess what type of SCM it is...

          We are having a problem with this plugin that is hosted on Assembla: https://wiki.jenkins-ci.org/display/JENKINS/Assembla+Auth+Plugin

          Show
          varsketiz Titas Norkūnas added a comment - If it is not github, it should just take the <url> tag from POM and not try to guess what type of SCM it is... We are having a problem with this plugin that is hosted on Assembla: https://wiki.jenkins-ci.org/display/JENKINS/Assembla+Auth+Plugin
          Hide
          Permalink
          oleg_nenashev Oleg Nenashev added a comment -

          Fixed the component

          Show
          oleg_nenashev Oleg Nenashev added a comment - Fixed the component

            People

            • Assignee:
              Unassigned
              Reporter:
              lynggaard lynggaard
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: