-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Master (Windows 7), Slaves (Windows 7, Ubuntu 14.04 LTS)
Jenkins: 2.7.1 LTS
Subversion plugin 2.6
I have several jobs building via subversion commit triggers.
The commit messages contain several lines with the majority in the following format:
Commiter Name: Details of change1. Details of change2.
Up to Jenkins version 1.651.1 + Subversion plugin 2.5.7, the build page displayed the commit message with several lines correctly under "change history".
After upgrading to Jenkins 1.651.3 + Subversion plugin 2.6 and now Jenkins 2.7.1 + Subversion plugin 2.6, the commit message is displayed as a single line.
For example, the commit message above would be displayed as follows:
Commiter Name:<br>Details of change1.<br>Details of change2.
Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as:
<br>
As a result, the commit message is being displayed as a single line.
- is related to
-
JENKINS-42740 Consider newline characters in commit messages also for summary of build changes section
-
- Open
-
[JENKINS-36521] Newline characters in commit logs not parsed correctly
Description |
Original:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
New:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
Component/s | Original: core [ 15593 ] |
Assignee | New: Manuel Recena Soto [ recena ] |
Description |
Original:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
New:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1 + Subversion plugin 2.5, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 + Subversion plugin 2.6 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
Description |
Original:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1 + Subversion plugin 2.5, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 + Subversion plugin 2.6 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
New:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1 + Subversion plugin 2.5, the build page displayed the commit message with several lines correctly under "change history". After upgrading to Jenkins 1.651.3 + Subversion plugin 2.6 and now Jenkins 2.7.1 + Subversion plugin 2.6, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
Description |
Original:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1 + Subversion plugin 2.5, the build page displayed the commit message with several lines correctly under "change history". After upgrading to Jenkins 1.651.3 + Subversion plugin 2.6 and now Jenkins 2.7.1 + Subversion plugin 2.6, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
New:
I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: {code} Commiter Name: Details of change1. Details of change2. {code} Up to Jenkins version 1.651.1 + Subversion plugin 2.5.7, the build page displayed the commit message with several lines correctly under "change history". After upgrading to Jenkins 1.651.3 + Subversion plugin 2.6 and now Jenkins 2.7.1 + Subversion plugin 2.6, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: {code} Commiter Name:<br>Details of change1.<br>Details of change2. {code} Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as: {code:html} <br> {code} As a result, the commit message is being displayed as a single line. |
Workflow | Original: JNJira [ 173234 ] | New: JNJira + In-Review [ 185011 ] |
Attachment | New: screenshot-missing-fix-in-summary.png [ 36356 ] |
Assignee | Original: Manuel Recena Soto [ recena ] | New: Łukasz Jąder [ ljader ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link | New: This issue is related to JENKINS-42740 [ JENKINS-42740 ] |