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

Robot Framework should show dates in the Test results Trend graph

    • 2.0.0

      Currently the Jenkins Robot Framework plugin shows the build number in the test results graph.

      It would be better to show dates in the Test results Trend graph.

      Even better it would be nice if I could make my own label formatter using DateTimeFormatter notation:
      https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html

          [JENKINS-35327] Robot Framework should show dates in the Test results Trend graph

          Dirk Richter added a comment -

          feature implemented in pull request 18: https://github.com/jenkinsci/robot-plugin/pull/18

          in robot section of global configuration now you can specify DateTimeFormatter string such as MM-dd HH:mm. Default is #$build for backward compatibility.

           

          Dirk Richter added a comment - feature implemented in pull request 18: https://github.com/jenkinsci/robot-plugin/pull/18 in robot section of global configuration now you can specify DateTimeFormatter string such as  MM-dd HH:mm. Default is #$build for backward compatibility.  

          Aleksi Simell added a comment -

          PR 18 merged.

          Aleksi Simell added a comment - PR 18 merged.

          Vitor Rego added a comment - - edited

          aleksisimell: Since this update when we set a custom build number suing Set Build Number plugin, the graph always shows the internal numbers and not our customized build number. How we can fix this?

          Vitor Rego added a comment - - edited aleksisimell : Since this update when we set a custom build number suing Set Build Number plugin, the graph always shows the internal numbers and not our customized build number. How we can fix this?

          Aleksi Simell added a comment -

          vitorego Could you open a new issue for this and assign it to me? I'm not really a fan of continuing discussion on a ticket that was closed almost 2 years ago. I'm not even sure do you mean the 2.0.0 released linked for this ticket or the newest release (2.1.2).

          Aleksi Simell added a comment - vitorego Could you open a new issue for this and assign it to me? I'm not really a fan of continuing discussion on a ticket that was closed almost 2 years ago. I'm not even sure do you mean the 2.0.0 released linked for this ticket or the newest release (2.1.2).

          Vitor Rego added a comment -

          It was done, thanks. JENKINS-63900

          Vitor Rego added a comment - It was done, thanks.  JENKINS-63900

            aleksisimell Aleksi Simell
            hjembaek Michael Hjembæk
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: