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

HTML in job description does not get rendered (all html tags escaped)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Ubuntu, Tomcat 7.0.52, jenkins war distribution

      We have html job descriptions for most of our jobs. Since upgrading to the latest jenkins version 1.553 (from 1.538) the html tags do not get rendered. Instead plain html code is shown.

      The same applies for the "Preview" when editing the job description.

          [JENKINS-22028] HTML in job description does not get rendered (all html tags escaped)

          Daniel Beck added a comment -

          Make sure Antisamy Markup Formatter plugin is installed and enabled.

          I think the almost 20 people watching this would have noticed in the last half year if this wasn't actually fixed and mentioned it. So it's likely that, whatever it is, you're experiencing a different issue. Therefore please file a new issue if the above doesn't work for you, following the advice at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue . Or even better, ask for troubleshooting advice on the jenkinsci-users mailing list or in IRC first.

          Daniel Beck added a comment - Make sure Antisamy Markup Formatter plugin is installed and enabled. I think the almost 20 people watching this would have noticed in the last half year if this wasn't actually fixed and mentioned it. So it's likely that, whatever it is, you're experiencing a different issue. Therefore please file a new issue if the above doesn't work for you, following the advice at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue . Or even better, ask for troubleshooting advice on the jenkinsci-users mailing list or in IRC first.

          Follow-up: I couldn't find Antisamy Plugin anywhere. We fixed it by enabling "OWASP Markup Formatter Plugin". The release notes of 1.553 do not explicitly name this plugin.

          Frank van Gemeren added a comment - Follow-up: I couldn't find Antisamy Plugin anywhere. We fixed it by enabling "OWASP Markup Formatter Plugin". The release notes of 1.553 do not explicitly name this plugin.

          Daniel Beck added a comment -

          Frank: That's the one. "OWASP Markup Formatter Plugin" is what it's called on the UI. Its ID is antisamy-markup-formatter, and its file name (in JENKINS_HOME/plugins) is antisamy-markup-formatter.hpi/jpi, so that's the name by which I know it. Sorry about that.

          Daniel Beck added a comment - Frank: That's the one. "OWASP Markup Formatter Plugin" is what it's called on the UI. Its ID is antisamy-markup-formatter, and its file name (in JENKINS_HOME/plugins) is antisamy-markup-formatter.hpi/jpi, so that's the name by which I know it. Sorry about that.

          I think that the naming of the option is misleading. The "Escaped HTML" suggests that if someone puts properly escaped HTML inside the description, it will get rendered (i.e. interpreted) - whereas it is actually treated as plaintext. Maybe naming the option as plain-text would serve better.

          Radek Antoniuk added a comment - I think that the naming of the option is misleading. The "Escaped HTML" suggests that if someone puts properly escaped HTML inside the description, it will get rendered (i.e. interpreted) - whereas it is actually treated as plaintext. Maybe naming the option as plain-text would serve better.

          Jesse Glick added a comment -

          warden file a PR to change the UI labels to refer to “plain text”.

          Jesse Glick added a comment - warden file a PR to change the UI labels to refer to “plain text”.

          Code changed in jenkins
          User: Radek Antoniuk
          Path:
          core/src/main/resources/hudson/markup/Messages.properties
          http://jenkins-ci.org/commit/jenkins/d758818b09ecd8d3eebebc927409e0ed58b2938a
          Log:
          JENKINS-22028 - update label to reflect actual behavior

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Radek Antoniuk Path: core/src/main/resources/hudson/markup/Messages.properties http://jenkins-ci.org/commit/jenkins/d758818b09ecd8d3eebebc927409e0ed58b2938a Log: JENKINS-22028 - update label to reflect actual behavior

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/resources/hudson/markup/Messages.properties
          http://jenkins-ci.org/commit/jenkins/107a502db4a55122f9be13ef0e31bebde8fe733d
          Log:
          Merge pull request #1742 from QUIDDIA/master

          JENKINS-22028 update label to reflect actual behavior

          Compare: https://github.com/jenkinsci/jenkins/compare/76f4c3519b62...107a502db4a5

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/markup/Messages.properties http://jenkins-ci.org/commit/jenkins/107a502db4a55122f9be13ef0e31bebde8fe733d Log: Merge pull request #1742 from QUIDDIA/master JENKINS-22028 update label to reflect actual behavior Compare: https://github.com/jenkinsci/jenkins/compare/76f4c3519b62...107a502db4a5

          Joseph Spencer added a comment - - edited

          Reopening as the initial fix only changed the display name, not the info message (see screenshot). Verified in 1.625.2

          Joseph Spencer added a comment - - edited Reopening as the initial fix only changed the display name, not the info message (see screenshot). Verified in 1.625.2

          Joseph Spencer added a comment - Pending PR https://github.com/kogosoftwarellc/jenkins/pull/1

          Daniel Beck added a comment -

          First, the message is true. It's just that you did not enable markup formatting, so there's no formatting applied.

          Second, nobody on this tracker cares about PRs to your own forks of Jenkins.

          Daniel Beck added a comment - First, the message is true. It's just that you did not enable markup formatting, so there's no formatting applied. Second, nobody on this tracker cares about PRs to your own forks of Jenkins.

            Unassigned Unassigned
            stefanthurnherr Stefan Thurnherr
            Votes:
            10 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: