[JIRA] (JENKINS-61757) Global Variable Reference HTML documentation strips <pre> tags

3 views
Skip to first unread message

r.fuereder@xortex.com (JIRA)

unread,
Mar 31, 2020, 8:55:02 AM3/31/20
to jenkinsc...@googlegroups.com
Reinhold Füreder created an issue
 
Jenkins / Bug JENKINS-61757
Global Variable Reference HTML documentation strips <pre> tags
Issue Type: Bug Bug
Assignee: Unassigned
Components: pipeline
Created: 2020-03-31 12:54
Priority: Major Major
Reporter: Reinhold Füreder

After quite some time I accidentally checked the "Pipeline Syntax > Global Variable Reference" for my shared Jenkins pipeline library and saw that the "<pre>" tags are now (unfortunately I can't remember when it was still OK, I just know that it used to be OK for a long time) stripped. Since it is about documentation of usage of shared pipeline library I claim that multi-line coding examples in such "<pre>"tags is fairly common...

Example: For a file called "acme.txt" with the following content

{{...
<p>
Example:
<pre>
acme.build {
node

{ ... }
}
</pre>
</p>
...}}

..., the resulting HTML will looks like:

{{
...
<p>
Example:
</p>
acme.build {
node { ... }

}
...
}}

And using an additional "<code>" inside the "<pre>" section, does not help either. But at least is kept...

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

r.fuereder@xortex.com (JIRA)

unread,
Mar 31, 2020, 8:56:02 AM3/31/20
to jenkinsc...@googlegroups.com
Reinhold Füreder updated an issue
Change By: Reinhold Füreder
After quite some time I accidentally checked the "Pipeline Syntax > Global Variable Reference" for my shared Jenkins pipeline library and saw that the "<pre>" tags are now (unfortunately I can't remember when it was still OK, I just know that it used to be OK for a long time) stripped. Since it is about documentation of usage of shared pipeline library I claim that multi-line coding examples in such "<pre>"tags is fairly common...

Example: For a file called "acme.txt" with the following content

{ { noformat}
...
    <p>
    Example:
      <pre>
  acme.build {
    node {
      ...
    }
  }
      </pre>
    </p>
...

{noformat
} }

..., the resulting HTML will looks like:

{ { noformat}
...
<p>
    Example:
      </p>
  acme.build {
    node {
      ...
    }
  }
...
{noformat } }

And using an additional "<code>" inside the "<pre>" section, does not help either. But at least is kept...
Reply all
Reply to author
Forward
0 new messages