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

display name can no longer be used as graph label

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • robot-plugin
    • Robot Framework plugin 2.1.2
    • 3.5.1

      Before the PR from JENKINS-35327, the build numbers we set using plugin Set Build Number was shown on the graph, after the PR was merged the trend graph always shows the internal build number and not our customized build number.

        1. image-2021-06-21-14-32-30-050.png
          image-2021-06-21-14-32-30-050.png
          28 kB
        2. image-2021-03-16-13-04-04-823.png
          image-2021-03-16-13-04-04-823.png
          185 kB
        3. image-2021-03-13-10-47-18-963.png
          image-2021-03-13-10-47-18-963.png
          28 kB
        4. image-2021-03-13-10-46-51-152.png
          image-2021-03-13-10-46-51-152.png
          21 kB
        5. image-2021-03-13-10-45-12-946.png
          image-2021-03-13-10-45-12-946.png
          15 kB
        6. image-2021-02-08-12-22-58-539.png
          image-2021-02-08-12-22-58-539.png
          19 kB
        7. image-2021-02-08-12-21-56-328.png
          image-2021-02-08-12-21-56-328.png
          10 kB
        8. image-2021-02-08-12-18-57-222.png
          image-2021-02-08-12-18-57-222.png
          25 kB
        9. image-2020-12-23-15-34-16-122.png
          image-2020-12-23-15-34-16-122.png
          23 kB
        10. image-2020-10-09-10-46-00-637.png
          image-2020-10-09-10-46-00-637.png
          320 kB

          [JENKINS-63900] display name can no longer be used as graph label

          Vitor Rego created issue -
          Aleksi Simell made changes -
          Issue Type Original: Improvement [ 4 ] New: Bug [ 1 ]
          Aleksi Simell made changes -
          Released As Original: 2.1.2
          Aleksi Simell made changes -
          Environment New: Robot Framework plugin 2.1.2

          Aleksi Simell added a comment -

          Hi vitorego,

          The PR you're referring to changed it so that the x-axel is configured from the Robot Framework section of the global configurations. By default it is  #$build. Can you try setting this value to the same value as you set with your customized build number? I'll check how easy this would be to overwrite when custom build number is used.

          Aleksi Simell added a comment - Hi vitorego , The PR you're referring to changed it so that the x-axel is configured from the Robot Framework section of the global configurations. By default it is   #$build . Can you try setting this value to the same value as you set with your customized build number? I'll check how easy this would be to overwrite when custom build number is used.

          Vitor Rego added a comment - - edited

          Hi aleksisimell, I did try to set the custom variable in the global configurations but did not work.

          Vitor Rego added a comment - - edited Hi aleksisimell , I did try to set the custom variable in the global configurations but did not work.

          Aleksi Simell added a comment -

          vitorego Can you please provide an example how you're setting your custom build number?

          Aleksi Simell added a comment - vitorego Can you please provide an example how you're setting your custom build number?
          Vitor Rego made changes -
          Attachment New: image-2020-12-23-15-34-16-122.png [ 53725 ]

          Vitor Rego added a comment -

          aleksisimell: here it is:

          We use a custom variable defined in the job.

           

          Vitor Rego added a comment - aleksisimell : here it is: We use a custom variable defined in the job.  

          Aleksi Simell added a comment -

          Thank you. I already created a pull request to resolve this issue, but I haven't created unit tests for that (yet), so I'll probably merge the change after Christmas break.

          Aleksi Simell added a comment - Thank you. I already created a pull request to resolve this issue, but I haven't created unit tests for that (yet), so I'll probably merge the change after Christmas break.

            aleksisimell Aleksi Simell
            vitorego Vitor Rego
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: