Done: https://issues.jenkins-ci.org/browse/JENKINS-22713
Thanks for your help/time, man! Let me know if I can do anything to
fix/resolve this.
Thx, S
On Mon, Apr 21, 2014 at 6:41 PM, Slide wrote:
> File an issue and I'll get to it when I can.
>
>
> On Mon, Apr 21, 2014 at 4:12 PM, Stephan Li
File an issue and I'll get to it when I can.
On Mon, Apr 21, 2014 at 4:12 PM, Stephan Lips wrote:
> Hmmm. So I looked at the src for CssInliner. Most interesting is that if
> the attribute data-inline="true" is set on an node, the image is
> retrieved, base64-encoded, and included inline. So
Hmmm. So I looked at the src for CssInliner. Most interesting is that if
the attribute data-inline="true" is set on an node, the image is
retrieved, base64-encoded, and included inline. So I did a li'l test,
where I referenced an image via URL, setting data-inline="true". And lo
and behold, th
Hmm, actually, it looks like the CssInliner could be doing something. It
processes anything that is text/html. I had forgotten about that because I
didn't write that part. There is currently not a way to turn it off.
On Mon, Apr 21, 2014 at 3:24 PM, Stephan Lips wrote:
> Nope, does not make a di
Nope, does not make a difference. I blank'd out all fields in the default
email configuration, and configured the ext-email plug-in overrides. '+'
characters in email content still arrive as +
Is some jenkins/ext-email dependency doing this?
Thx, S
On Mon, Apr 21, 2014 at 3:59 PM, Slide wrot
Email-ext DOES have it's own server configuration, you just have to check
"override default settings" in the global config. That would be another
thing to try, overriding the default settings so that the session is
created completely in email-ext.
On Mon, Apr 21, 2014 at 12:37 PM, Stephan Lips wr
If I check 'save to workspace' the '+' chars are not being escaped with
+.
FWIW, I also tried a couple different email providers (my corporate smtp
server, and google), in both cases the arriving email had the '+'
substituted for ". Since ext-email does not have its own mail server
configuration,
I don't know of anything in the email-ext code that would escape anything
like you are describing. Can you try checking the "save to workspace"
checkbox in the project settings and see if the same escaping is shown in
the saved off file?
On Mon, Apr 21, 2014 at 11:08 AM, Stephan Lips wrote:
> Ye
Yes, the issue reproduces with a template. Curiously, when testing the
template (through the 'Email Template Testing' link in the workspace), the
inserted base64 string renders correctly. The received email, however,
still sees the + escapes instead of the '+' char, causing the base64
img src to
Yes, I'd like you to try and see if the issue occurs with a template.
On Apr 21, 2014 6:49 AM, "Stephan Lips" wrote:
> It reproduces without any templates. Simply put the following in the
> 'Default Content' field of the ext-email configuration:
>
>
> a+b
>
> The email received will show the ab
It reproduces without any templates. Simply put the following in the
'Default Content' field of the ext-email configuration:
a+b
The email received will show the above as
a+b
(note the " in place of the '+' signs).
Thx,
- S
On Fri, Apr 18, 2014 at 8:37 PM, Slide wrote:
> Can you try
Can you try using a groovy template instead of just trying to generate the
HTML yourself? I'm not sure why the text is being encoded like you mention.
I can try and recreate if you send the file you are using and the template.
On Apr 18, 2014 5:48 PM, "stephanl" wrote:
> So then, do you know if t
So then, do you know if there is a way to send a base64 as-is in an email?
E.g. without being html-escaped implicitly? Looks like some macro tokens
support this, through the escapeHtml attribute. I did not see anything in
the ext-email code base suggesting there is a global option/switch, or
There is no capability to add a different content type.
On Fri, Apr 18, 2014 at 1:16 PM, stephanl wrote:
> HTML (text/html). For grins, I tried Plain Text (text/plain), in which
> case the base64 string was included un-escaped, but (of course) not
> recognized/rendered as image when the contai
HTML (text/html). For grins, I tried Plain Text (text/plain), in which
case the base64 string was included un-escaped, but (of course) not
recognized/rendered as image when the containing email was viewed. In the
configuration section of the ext-email plugin these are the only two
options (te
What is your content type set to in the settings?
On Fri, Apr 18, 2014 at 12:52 PM, stephanl wrote:
> Not using templates. Tried using
>
>
> width="900" height="550"/>
>
> in the 'Default Content' section/field of the ext-email plugin. Also
> tried using
>
> def reportPath = build.getWorkspa
Not using templates. Tried using
in the 'Default Content' section/field of the ext-email plugin. Also tried
using
def reportPath = build.getWorkspace().child("my-base64-encoded-png.b64")
msg.setContent("", "text/html");
as pre-send script (also in the ext-email plugin, Advanced section)
Are you using a groovy or jelly template, or generating the HTML yourself?
On Fri, Apr 18, 2014 at 10:20 AM, stephanl wrote:
> Howdy,
>
> I am trying to embed a base64 img src in the body/content of an ext-email
> notification, like so:
>
>
>
> The email I receive has all '+' characters in the
18 matches
Mail list logo
