• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • ci cd server

      Please see attached screengrab. The text in a job build history that exceeds 2 digit representation has a zero length space inserted after the first digit, so a job '#321 ' becomes '#3​21 ' and is then not navigatable via xpath when used with testing frameworks relying on the Selenium web driver.

      I also see there is another issue related to zero length space at https://issues.jenkins-ci.org/browse/JENKINS-28022

      Thank you in advance.

          [JENKINS-38666] Zero Length Space character in build history

          Daniel Beck added a comment -

          Distinct from JENKINS-28022. Probably a bug in whatever code adds zero-width-spaces, I cannot think of a situation in which build numbers need that (at least not before going into the 5 digits or so).

          Daniel Beck added a comment - Distinct from JENKINS-28022 . Probably a bug in whatever code adds zero-width-spaces, I cannot think of a situation in which build numbers need that (at least not before going into the 5 digits or so).

            Unassigned Unassigned
            alexglx Alex Golovin
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: