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

HTML in Set Build Description no longer honored

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Running Jenkins on 2K3 server using Master-Slave configuration. Master and all slaves are windows services.

      HTML hyperlink that was added as part of the build process to the build description, to allow users to click and link to external information/tool with information specific to each successful build, is no longer honored, despite neither a change to the produced description output or the description setter plugin. Suspect some formating is clipping the anker tag entry.

      After doing some research I encountered a problem with how the html was parsed and stored in the build xml file.

      An example html anker tage being stored is written as follows:

      <a href="javascript: function openPopup()

      {window.open('http://xxxxxx/iscmstrigger?IscmsBuildName=Actuarial2&SvnRevision=1670&CiBuildNumber=13&IscmsExtension=STG&IscmsCustomExt=SEP12CH_1670&ISCMSTargets=TPCSBXW1 : ACTUARIAL2,TPCSBXA1 : ACTUARIAL2,TPCSBXW3 : ACTUARIAL2,TPCSBXA3 : ACTUARIAL2,TPCQA2W3: ACTUARIAL2,TPCQA2A3: ACTUARIAL2','test','toolbar=no,menubar=no,width=300,height=250,resizable=yes, left=430, top=23');}

      openPopup();">ISCMS Build</a>

      However, what gets stored in the XML looks like this:

      <a href="javascript: function openPopup()

      {window.open('http://xxxxxx/iscmstrigger?IscmsBuildName=Actuarial2&SvnRevision=1670&CiBuildNumber=13&IscmsExtension=STG&IscmsCustomExt=SEP12CH_1670&ISCMSTargets=TPCSBXW1 : ACTUARIAL2,TPCSBXA1 : ACTUARIAL2,TPCSBXW3 : ACTUARIAL2,TPCSBXA3 : ACTUARIAL2,TPCQA2W3: ACTUARIAL2,TPCQA2A3: ACTUARIAL2','test','toolbar=no,menubar=no,width=300,height=250,resizable=yes, left=430, top=23');}

      openPopup();">ISCMS Build</a>

      When I look at http://en.wikipedia.org/wiki/Character_encodings_in_HTML I see that the "&apos" tag is discouraged (doesn't work), and that what should be used is "&#39" or "&#x0027". Whatever encoding gets used to parse and store my original html anker tag into the build.xml needs to be fixed, or whatever is reading it back when displaying has to be reverted.

            huybrechts huybrechts
            alexlombardi alexlombardi
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: