-
Bug
-
Resolution: Duplicate
-
Minor
-
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 '#321 ' 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.
- duplicates
-
JENKINS-28022 Build description longer than 30 chars has hex zero width space added
-
- Closed
-
[JENKINS-38666] Zero Length Space character in build history
Link |
New:
This issue is related to |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Link |
Original:
This issue is related to |
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).