-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
ECharts API Plugin 5.2.2-1, Warnings Next Generation 9.8.0
When specifying a recordIssues pipeline step tool name that contains + characters, those + characters are replaced with the escape sequence (ampersand pound 43 semicolon) when presented on trend chart titles and in the build summary. There may be other characters besides + effected by this issue.
For example, the attached screenshots result from this:
recordIssues tools: [clang(name: 'clang++ 11.x c++17', id: 'clang11_cpp17', pattern: 'build_log')]
- depends on
-
JENKINS-67101 C++ Lint shows as C++ Lint
-
- Open
-
- links to
[JENKINS-67245] warnings-ng recordIssues tool names presented with html escape codes
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Description |
Original:
When specifying a recordIssues pipeline step tool name that contains + characters, those + characters are replaced with + when presented on trend chart titles and in the build summary. There may be other characters besides + effected by this issue.
For example, the attached screenshots result from this: recordIssues tools: [clang(name: 'clang++ 11.x c++17', id: 'clang11_cpp17', pattern: 'build_log')] |
New:
When specifying a recordIssues pipeline step tool name that contains + characters, those + characters are replaced with the escape sequence (ampersand pound 43 semicolon) when presented on trend chart titles and in the build summary. There may be other characters besides + effected by this issue.
For example, the attached screenshots result from this: recordIssues tools: [clang(name: 'clang++ 11.x c++17', id: 'clang11_cpp17', pattern: 'build_log')] |
Attachment | New: left-side-panel-link-correct-escape-chars.png [ 56859 ] | |
Attachment | New: stage-view-correct-escape-chars.png [ 56860 ] |
Resolution | Original: Won't Fix [ 2 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Link | New: This issue depends on JENKINS-67101 [ JENKINS-67101 ] |
It is necessary to escape all characters to avoid security problems (all user provided content needs to be piped through our HTML sanitizer).