-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 1.596.1, 2.124
-
-
Jenkins 2.276
We use a Groovy script to write the package version into the build description of a job after it completes. Users then copy this from the Jenkins UI and paste it to perform a deploy. I have discovered occasional strange issues with this where what seems to be a valid version number is not found by our deploy system. Eventually I figured out that Jenkins is inserting a
​
in the string if it exceeds 30 chars. This is invisible (obviously) in the UI but gets captured when the text is selected and copied/pasted (at least with Chrome on MacOS). This is a problem because this copy-paste workflow has been embedded here for several years, and a recent Jenkins upgrade has thrown this entropy into it
- is blocking
-
JENKINS-40663 strings cut-n-pasted from Description should not contain NUL or VT
-
- Resolved
-
- is duplicated by
-
JENKINS-38666 Zero Length Space character in build history
-
- Fixed but Unreleased
-
-
JENKINS-40663 strings cut-n-pasted from Description should not contain NUL or VT
-
- Resolved
-
- is related to
-
JENKINS-26406 Build history text field wrap fails when containing markup
-
- Resolved
-
- relates to
-
JENKINS-39443 Sanitise description string as it may contains troublesome chars
-
- Closed
-
[JENKINS-28022] Build description longer than 30 chars has hex zero width space added
Assignee | Original: Daniel Beck [ danielbeck ] | |
Description | Original: We use a Groovy script to write the package version into the build description of a job after it completes. Users then copy this from the Jenkins UI and paste it to perform a deploy. I have discovered occasional strange issues with this where what seems to be a valid version number is not found by our deploy system. Eventually I figured out that Jenkins is inserting a ​ in the string if it exceeds 30 chars. This is invisible (obviously) in the UI but gets captured when the text is selected and copied/pasted (at least with Chrome on MacOS). This is a problem because this copy-paste workflow has been embedded here for several years, and a recent Jenkins upgrade has thrown this entropy into it :) | New: We use a Groovy script to write the package version into the build description of a job after it completes. Users then copy this from the Jenkins UI and paste it to perform a deploy. I have discovered occasional strange issues with this where what seems to be a valid version number is not found by our deploy system. Eventually I figured out that Jenkins is inserting a {code}​{code} in the string if it exceeds 30 chars. This is invisible (obviously) in the UI but gets captured when the text is selected and copied/pasted (at least with Chrome on MacOS). This is a problem because this copy-paste workflow has been embedded here for several years, and a recent Jenkins upgrade has thrown this entropy into it :) |
Workflow | Original: JNJira [ 162624 ] | New: JNJira + In-Review [ 180996 ] |
Link |
New:
This issue is blocking |
Link |
New:
This issue is duplicated by |
Why is this assigned to me?