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

Usage plugin incorrectly reports multi-project

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • plugin-usage-plugin
    • Jenkins-2.121.3
      matrix-project-1.12
      plugin-usage-plugin-0.4

    Description

      Create a Multi-Configuration project (eg: Multi-Job), 

      configure to run 2 on 2 slaves (eg: 2273, 2274),

      Displays in Plugin Usage as:
      <plugin-name> |  <ver> | <QTY> |

      • 2273 ( http://${JENKINS_URL}/job/Multi-Job/label=2273/ )
      • 2274 ( http://${JENKINS_URL}/job/Multi-Job/label=2274/ )

      Should just process the jobName (Multi-Job), not the labelName

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53265 Usage plugin incorrectly reports multi-project

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            froque Filipe Roque added a comment -

            I can't reproduce based on the available information. Please provide more information.

            Does this bug still happen?

            froque Filipe Roque added a comment - I can't reproduce based on the available information. Please provide more information. Does this bug still happen?
            ianw Ian Williams added a comment - - edited

            Running 263.4 + plugin-usage:1.1
            Steps to reproduce:
            Create Multi-configuration project (job/admin/job/Multi),
            Configure axis by label:

            <axes>
               <hudson.matrix.LabelAxis>
            {{ <name>label</name>}}
                 <values>
                   <string>LNX_A</string>
                   <string>LNX_B</string>
                 </values>
                </hudson.matrix.LabelAxis>
             </axes>

            Examine Plugin-Usage (/pluginusage/) and observe:

            •admin » Multi » LNX_A
            •admin » Multi » LNX_B

            ${JENKINS_URL}/job/admin/job/Multi/label=LNX_A/
            ${JENKINS_URL}/job/admin/job/Multi/label=LNX_B/

            There is only one job so one job configuration (ie: plugins), yet the usage is reported per label. This gets weird if you have dozens of nodes.

            Further problem. When ch1anging axis configuration, say to label= [compass, docker ], removing the originals, now see all four values:

            •admin » Multi » LNX_A
            •admin » Multi » LNX_B
            •admin » Multi » compass
            •admin » Multi » docker

            As if it's analyzing the logs, not the jobs.

            ianw Ian Williams added a comment - - edited Running 263.4 + plugin-usage:1.1 Steps to reproduce: Create Multi-configuration project (job/admin/job/Multi), Configure axis by label: <axes>    <hudson.matrix.LabelAxis> {{ <name>label</name>}}      <values>        <string>LNX_A</string>        <string>LNX_B</string>      </values>     </hudson.matrix.LabelAxis>  </axes> Examine Plugin-Usage (/pluginusage/) and observe: •admin » Multi » LNX_A •admin » Multi » LNX_B ${JENKINS_URL}/job/admin/job/Multi/label=LNX_A/ ${JENKINS_URL}/job/admin/job/Multi/label=LNX_B/ There is only one job so one job configuration (ie: plugins), yet the usage is reported per label. This gets weird if you have dozens of nodes. Further problem. When ch1anging axis configuration, say to label= [compass, docker ] , removing the originals, now see all four values: •admin » Multi » LNX_A •admin » Multi » LNX_B •admin » Multi » compass •admin » Multi » docker As if it's analyzing the logs, not the jobs.

            People

              Unassigned Unassigned
              ianw Ian Williams
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: