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

Build description longer than 30 chars has hex zero width space added

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 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

          [JENKINS-28022] Build description longer than 30 chars has hex zero width space added

          Owen Mehegan created issue -
          Daniel Beck made changes -
          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 :)
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 162624 ] New: JNJira + In-Review [ 180996 ]
          Daniel Beck made changes -
          Link New: This issue is blocking JENKINS-40663 [ JENKINS-40663 ]
          Mark Hudson made changes -
          Link New: This issue is duplicated by JENKINS-40663 [ JENKINS-40663 ]
          Mark Hudson made changes -
          Link New: This issue relates to JENKINS-39443 [ JENKINS-39443 ]
          Thomas De Schampheleire made changes -
          Environment Original: Jenkins 1.596.1 New: Jenkins 1.596.1, 2.124
          Greg Dubicki made changes -
          Link New: This issue is related to JENKINS-38666 [ JENKINS-38666 ]
          Greg Dubicki made changes -
          Link New: This issue is related to JENKINS-26406 [ JENKINS-26406 ]
          Greg Dubicki made changes -
          Link New: This issue is duplicated by JENKINS-38666 [ JENKINS-38666 ]
          Greg Dubicki made changes -
          Link Original: This issue is related to JENKINS-38666 [ JENKINS-38666 ]

            Unassigned Unassigned
            owenmehegan Owen Mehegan
            Votes:
            19 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated:
              Resolved: