Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
We use the extended email notification plugin and its regex tokens to email a section of the console output. That section is a basic HTML with a few <pre> tags that are pre formatted. After the latest update of both the plugin and jenkins, the section of the console output started getting a "tidyhtml" treatment.
Old email source and console output looked like this:
<html>
<head></head>
<body>
<table border="1">
<tbody>
<tr>
<td> <b>TEXT</b> </td>
<td> <b>TEXT</b><pre>
line
line<v1>line
line<v1>line
...
New email source looks like this (and messing up the actual email):
<html>
<head></head>
<body>
<table border="1">
<tbody>
<tr>
<td> <b>TEXT</b> </td>
<td> <b>TEXT</b><pre>
line
line
<v1>
line
line
<v1>
line
...
While I don't mind indentation and pretty printing, it seems like a bug to try to beautify (by introducing new lines and spaces) the output of a console.
EDIT: alright, looks like jira clears any leading blanks so I'll use * to indicate space.
New output:
<html>
*<head></head>
**<body>
***<table border="1">
***<tbody>
****<tr>
*****<td> <b>TEXT</b> </td>
*****<td> <b>TEXT</b><pre>
line
line
******<v1>
*******line
line
*******<v1>
********line
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
We use the extended email notification plugin and its regex tokens to email a section of the console output. That section is a basic HTML with a few <pre> tags that are pre formatted. After the latest update of both the plugin and jenkins, the section of the console output started getting a "tidyhtml" treatment. Old email source and console output looked like this: <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line<v1>line line<v1>line ... New email source looks like this (and messing up the actual email): <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line <v1> line line <v1> line ... While I don't mind indentation and pretty printing, it seems like a bug to try to beautify (by introducing new lines and spaces) the output of a console. |
We use the extended email notification plugin and its regex tokens to email a section of the console output. That section is a basic HTML with a few <pre> tags that are pre formatted. After the latest update of both the plugin and jenkins, the section of the console output started getting a "tidyhtml" treatment. Old email source and console output looked like this: <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line<v1>line line<v1>line ... New email source looks like this (and messing up the actual email): <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line <v1> line line <v1> line ... While I don't mind indentation and pretty printing, it seems like a bug to try to beautify (by introducing new lines and spaces) the output of a console. EDIT: alright, looks like jira clears any leading blanks so I'll use * to indicate space. New output: <html> *<head></head> **<body> ***<table border="1"> ***<tbody> ****<tr> *****<td> <b>TEXT</b> </td> *****<td> <b>TEXT</b><pre> line line ******<v1> ******line line *******<v1> *******line |
Description |
We use the extended email notification plugin and its regex tokens to email a section of the console output. That section is a basic HTML with a few <pre> tags that are pre formatted. After the latest update of both the plugin and jenkins, the section of the console output started getting a "tidyhtml" treatment. Old email source and console output looked like this: <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line<v1>line line<v1>line ... New email source looks like this (and messing up the actual email): <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line <v1> line line <v1> line ... While I don't mind indentation and pretty printing, it seems like a bug to try to beautify (by introducing new lines and spaces) the output of a console. EDIT: alright, looks like jira clears any leading blanks so I'll use * to indicate space. New output: <html> *<head></head> **<body> ***<table border="1"> ***<tbody> ****<tr> *****<td> <b>TEXT</b> </td> *****<td> <b>TEXT</b><pre> line line ******<v1> ******line line *******<v1> *******line |
We use the extended email notification plugin and its regex tokens to email a section of the console output. That section is a basic HTML with a few <pre> tags that are pre formatted. After the latest update of both the plugin and jenkins, the section of the console output started getting a "tidyhtml" treatment. Old email source and console output looked like this: <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line<v1>line line<v1>line ... New email source looks like this (and messing up the actual email): <html> <head></head> <body> <table border="1"> <tbody> <tr> <td> <b>TEXT</b> </td> <td> <b>TEXT</b><pre> line line <v1> line line <v1> line ... While I don't mind indentation and pretty printing, it seems like a bug to try to beautify (by introducing new lines and spaces) the output of a console. EDIT: alright, looks like jira clears any leading blanks so I'll use * to indicate space. New output: <html> *<head></head> **<body> ***<table border="1"> ***<tbody> ****<tr> *****<td> <b>TEXT</b> </td> *****<td> <b>TEXT</b><pre> line line ******<v1> *******line line *******<v1> ********line |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Workflow | JNJira [ 148939 ] | JNJira + In-Review [ 192953 ] |
My guess is that this is from the cssinliner. I'll take a look