-
Bug
-
Resolution: Unresolved
-
Major
-
jenkins 2.173 ( current version installed - definitely did not start with this version )
Plugins - all installed plugins are the latest versions.
Clearcase plug-in 1.6.3
Simple dynamic clearcase 1.2.2
Web browser - Chrome , but irrelevant ( also on IE )
Running through reverse proxy :
ProxyPass /jenkins https://localhost:8081/jenkins nocanon
ProxyPassReverse /jenkins https://localhost:8081/jenkins
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline';"
jenkins 2.173 ( current version installed - definitely did not start with this version ) Plugins - all installed plugins are the latest versions. Clearcase plug-in 1.6.3 Simple dynamic clearcase 1.2.2 Web browser - Chrome , but irrelevant ( also on IE ) Running through reverse proxy : ProxyPass /jenkins https://localhost:8081/jenkins nocanon ProxyPassReverse /jenkins https://localhost:8081/jenkins Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline';"
The clearcase changelog is no longer correctly displayed.
All comments are concatenated into one line.
- An end of line is changed to <br> and when looking at html source it contains <br>
- changelog.xml contains " and " appears in source html ( can be fixed by modifying changelog.xml changing " to " )
Original ( in changelog.xml )
<user>myUserName</user>
<comment>My Change Comment
the second line of my comment
</comment>
Jenkins Job - Recent Changes
#1234 ( Apr 10, 2019 ...)
1. myUserName detail My Change Comment*<br>the second line of my comment<br>*
html page source
class="changeset-message"><b>1. <a href="/jenkins/user/myUser/">myUserName</a> on 16/04/2019 13:22:59</b><br />
My Change Comment*<br>the second line of my comment <br>*
( The display of the actual text is converted - the text contains
amp lt;br>
even here the <br> is converted ) - edit to see input text
I can't remember when it first happened, could have been the change from http to https 
Could also be the configuration of the ReverseProxy
