• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: robot-plugin
• Labels:

  • robocon2022
• Environment:

  Robot Framework plugin 2.1.2

1. 

   image-2020-10-09-10-46-00-637.png

   320 kB

   2020-10-09 09:46

2. 

   image-2020-12-23-15-34-16-122.png

   23 kB

   2020-12-23 15:34

3. 

   image-2021-02-08-12-18-57-222.png

   25 kB

   2021-02-08 12:18

4. 

   image-2021-02-08-12-21-56-328.png

   10 kB

   2021-02-08 12:21

5. 

   image-2021-02-08-12-22-58-539.png

   19 kB

   2021-02-08 12:22

6. 

   image-2021-03-13-10-45-12-946.png

   15 kB

   2021-03-13 10:45

7. 

   image-2021-03-13-10-46-51-152.png

   21 kB

   2021-03-13 10:46

8. 

   image-2021-03-13-10-47-18-963.png

   28 kB

   2021-03-13 10:47

9. 

   image-2021-03-16-13-04-04-823.png

   185 kB

   2021-03-16 13:04

10. 

    image-2021-06-21-14-32-30-050.png

    28 kB

    2021-06-21 13:32

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

Load more older comments

Collapse comment: Aleksi Simell added a comment - 2021-03-12 13:08

Aleksi Simell added a comment - 2021-03-12 13:08

New version released (it will take up to 8 hours to show in update-center).

Expand comment: Aleksi Simell added a comment - 2021-03-12 13:08

Aleksi Simell added a comment - 2021-03-12 13:08 New version released (it will take up to 8 hours to show in update-center).

Collapse comment: Vitor Rego added a comment - 2021-03-13 10:46, Edited by Vitor Rego - 2021-03-13 10:47

Vitor Rego added a comment - 2021-03-13 10:46 - edited

Hi aleksisimell, I´m not sure if version 3.0.0 might fix the issue, but still not fixed:

If I set the variable I want in the global settings, the graph does not show anything, even after I clean by browser´s cache:

 

Expand comment: Vitor Rego added a comment - 2021-03-13 10:46, Edited by Vitor Rego - 2021-03-13 10:47

Vitor Rego added a comment - 2021-03-13 10:46 - edited Hi aleksisimell , I´m not sure if version 3.0.0 might fix the issue, but still not fixed: If I set the variable I want in the global settings, the graph does not show anything, even after I clean by browser´s cache:  

Collapse comment: Aleksi Simell added a comment - 2021-03-13 11:04

Aleksi Simell added a comment - 2021-03-13 11:04

vitorego you can specify the label per job now. Try that.

Expand comment: Aleksi Simell added a comment - 2021-03-13 11:04

Aleksi Simell added a comment - 2021-03-13 11:04 vitorego you can specify the label per job now. Try that.

Collapse comment: Aleksi Simell added a comment - 2021-03-15 11:08

Aleksi Simell added a comment - 2021-03-15 11:08

vitorego Did configuring the label for the job resolve your issue?

Expand comment: Aleksi Simell added a comment - 2021-03-15 11:08

Aleksi Simell added a comment - 2021-03-15 11:08 vitorego Did configuring the label for the job resolve your issue?

Collapse comment: Vitor Rego added a comment - 2021-03-16 13:04

Vitor Rego added a comment - 2021-03-16 13:04

Hi aleksisimell, using the setting per job the graph is updated, however all builds in the graph are updated with the latest build:

Expand comment: Vitor Rego added a comment - 2021-03-16 13:04

Vitor Rego added a comment - 2021-03-16 13:04 Hi aleksisimell , using the setting per job the graph is updated, however all builds in the graph are updated with the latest build:

Collapse comment: Aleksi Simell added a comment - 2021-03-18 06:14, Edited by Aleksi Simell - 2021-03-18 06:15

Aleksi Simell added a comment - 2021-03-18 06:14 - edited

I'm actually genuinely surprised that has even worked in the first place. Digging back to earlier PR it used NumberOnlyBuildLabel, which is supposed to return integers only.

Expand comment: Aleksi Simell added a comment - 2021-03-18 06:14, Edited by Aleksi Simell - 2021-03-18 06:15

Aleksi Simell added a comment - 2021-03-18 06:14 - edited I'm actually genuinely surprised that has even worked in the first place. Digging back to earlier PR it used NumberOnlyBuildLabel , which is supposed to return integers only.

Collapse comment: Aleksi Simell added a comment - 2021-06-21 12:44

Aleksi Simell added a comment - 2021-06-21 12:44

Reopening the issue again, as this is clearly not fixed yet.

Expand comment: Aleksi Simell added a comment - 2021-06-21 12:44

Aleksi Simell added a comment - 2021-06-21 12:44 Reopening the issue again, as this is clearly not fixed yet.

Collapse comment: Vitor Rego added a comment - 2021-06-21 13:32

Vitor Rego added a comment - 2021-06-21 13:32

The graph now is showing the build number, but the same buid number (the last one) is used for all the runs:

Expand comment: Vitor Rego added a comment - 2021-06-21 13:32

Vitor Rego added a comment - 2021-06-21 13:32 The graph now is showing the build number, but the same buid number (the last one) is used for all the runs:

Collapse comment: Aleksi Simell added a comment - 2024-02-21 13:58

Aleksi Simell added a comment - 2024-02-21 13:58

Finally managed to fix this. Pull Request created to fix this issue. The root cause is that you don't actually want to use build number as the label, but rather the build display name. This PR adds possibility to use display name as the label.

Expand comment: Aleksi Simell added a comment - 2024-02-21 13:58

Aleksi Simell added a comment - 2024-02-21 13:58 Finally managed to fix this. Pull Request created to fix this issue. The root cause is that you don't actually want to use build number as the label, but rather the build display name . This PR adds possibility to use display name as the label.

Collapse comment: Aleksi Simell added a comment - 2024-02-22 10:29

Aleksi Simell added a comment - 2024-02-22 10:29

PR merged. Fix will be available in the next release.

Expand comment: Aleksi Simell added a comment - 2024-02-22 10:29

Aleksi Simell added a comment - 2024-02-22 10:29 PR merged. Fix will be available in the next release.