OS: Windows 10
Jenkins: 2.414.1 (war install)
Email Extension Plugin: v2.100
Good day... having issues getting this plugin functioning.
I'm using the exact same settings when testing the standard Email Plugin
which is working fine, but when trying to use this plugin so I can attach
test
I did and it works.
On Tuesday, June 9, 2020 at 2:40:44 PM UTC-4, slide wrote:
>
> You can set the classpath in the global configuration for email-ext.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and
You can set the classpath in the global configuration for email-ext.
On Tue, Jun 9, 2020 at 10:56 AM Mario Jauvin wrote:
> What is the classpath setup at that moment? What do I have access to?
>
> On Tuesday, June 9, 2020 at 1:34:54 PM UTC-4, slide wrote:
>>
>> No, this scenario is not
What is the classpath setup at that moment? What do I have access to?
On Tuesday, June 9, 2020 at 1:34:54 PM UTC-4, slide wrote:
>
> No, this scenario is not currently supported.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
No, this scenario is not currently supported.
On Tue, Jun 9, 2020 at 9:46 AM Mario Jauvin wrote:
> I am trying to use groovy classes found in the pipeline shared library
> (using @Library annotation on jenkinsfile) inside the presendScript string
> supplied to the emailext pipeline step. These
I am trying to use groovy classes found in the pipeline shared library
(using @Library annotation on jenkinsfile) inside the presendScript string
supplied to the emailext pipeline step. These classes come from the src
folder of the shared library (not the vars folder). I get
It turned out that the problem was not in the jenkins or the plugin code
but rather in the configuration of the test active directory domain that
was being used. Thanks for all the help.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
I check and with ActiveDirectoryAuthenticationProvider the email address
appears. It is in ActiveDirectoryMailAddressResolverImpl where the email
is null.
I suspect that the issue is in the method updateUserInfo in
ActiveDirectoryUserDetail. I will try to debug it. It took quite a while
to
I am not super familiar with the AD plugin, so I am not sure why it would
be returning null. Maybe you can raise an issue on Jira (when its back up)
for that plugin.
On Thu, Jun 4, 2020 at 1:04 PM Mario Jauvin wrote:
> the user exists and has an email address in the mail attribute.
>
> On
the user exists and has an email address in the mail attribute.
On Thursday, June 4, 2020 at 2:37:15 PM UTC-4, slide wrote:
>
> Does your AD implementation put the email address in a non-standard
> attribute? Does the user ID exist in the AD and does that user account have
> a valid email
Does your AD implementation put the email address in a non-standard
attribute? Does the user ID exist in the AD and does that user account have
a valid email address attribute?
On Thu, Jun 4, 2020 at 10:57 AM Mario Jauvin wrote:
> I noticed that the error comes from
I noticed that the error comes from ActiveDirectoryMailAddressResolverImpl
in the active_directory plugin. Any suggestion? Is this a problem with the
plugin or with the configuration?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
I am using the active directory plugin and found out the following debug
log output:
Resolving e-mail address for "Smith, Jim" ID=abc456
Jun 04, 2020 1:36:42 PM FINE
hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider
Login successful: abc456
Do you have the LDAP plugin installed and configured? There needs to be a
mechanism that the username can be converted to a an email address, this is
called a MailAddressResolver (
javadoc.jenkins.io/plugin/mailer/hudson/tasks/MailAddressResolver.html).
Several SCM plugins implement a
Is there some diagnostics or debugging I can turn on to troubleshoot this?
On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer wrote:
>
> We are reading the mail addresses from ldap. The assignment user from repo
> commit user to mail address happens automagically in the background.
Obviously the userid and domain have been camouflaged to protect the
innocents.
On Thursday, June 4, 2020 at 10:06:53 AM UTC-4, Mario Jauvin wrote:
>
> This is the output in the pipeline job:
>
> Sending email to: abc...@company.com
>
> This does not work in our organization. What could be the
This is the output in the pipeline job:
Sending email to: abc...@company.com
This does not work in our organization. What could be the problem?
On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer wrote:
>
> We are reading the mail addresses from ldap. The assignment user from repo
This is what I thought but the automagical functionality requires an
incantation because it is not working. Any suggestions? I have updated
all plugins and jenkins to their latest most recent version. It still does
not work.
On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer
We are reading the mail addresses from ldap. The assignment user from repo
commit user to mail address happens automagically in the background.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving
I had not. I added the domain but our email system does not accept
abc...@company.com. One must use firstname.lastn...@company.com. This
information is found in active directory or I believe can be retrieved
using ldap. Any solutions?
On Thursday, June 4, 2020 at 8:58:25 AM UTC-4, slide
Did you setup the default domain in the global configuration?
On Thu, Jun 4, 2020, 05:54 Mario Jauvin wrote:
>
> I have noticed that when using DevelopersRecipientProvider in the
> declarative pipeline, the information returned is the userid and not the
> email address. I get the error:
>
>
I have noticed that when using DevelopersRecipientProvider in the declarative
pipeline, the information returned is the userid and not the email address. I
get the error:
Error sending to the following INVALID addresses: abc543
abc543 is the user that committed a change.
I also noticed that
It looks like you might be mixing up some usages..if the variable is an
environment variable (and that is the only type that will work in a
template), you'd want to do something like this:
<% ENV(var:"MYTOOL_VERSION") %>
This may only work with the most recent email-ext version.
On Thu, Mar 28,
Hi All,
I wish to send some parameter/ variable from the current build job to the
Email template to send it in an email.
I have saved my email template as Manage_Jenkins>> Managed_Files >>
custom_groovy_Email.groovy
in email template, I am trying to use it as follows
Duration:
e(Run.java:1791)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute=method>
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run=method>
> at hudson.model.Resou
43)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run=method>
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute=method>
>
od>
at hudson.model.Executor.run(Executor.java:374)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run=method>
Finished: SUCCESS
Email Extension Plugin
<http://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin>
This plugin is a replacement for
The messages are always sent as multipart, even for plain text messages.
On Thu, Oct 13, 2016, 07:15 Adri CS wrote:
> Hi slide,
>
> yes. That was it! Thanks!
>
> Altough why is the content being reported as multipart when it's a plain
> text string?
>
> Cheers!
>
>
> On
Hi slide,
yes. That was it! Thanks!
Altough why is the content being reported as multipart when it's a plain
text string?
Cheers!
On Thursday, 13 October 2016 15:57:35 UTC+2, slide wrote:
>
> You are missing double quotes around the variable.
>
> logger.println("${PROJECT_DEFAULT_CONTENT}");
You are missing double quotes around the variable.
logger.println("${PROJECT_DEFAULT_CONTENT}");
On Thu, Oct 13, 2016, 06:44 Adri CS wrote:
> Dear all,
>
> In a project, I'm trying to access to the message contents in the
> *Pre-send script.*I'm trying to add those
Dear all,
In a project, I'm trying to access to the message contents in the
*Pre-send script.*I'm trying to add those contents to the log.
I've set up the message type directly to *text/plain* and specified the
*Default
Contents* to a string (let's say: "ABCDEF").
So in the *Pre-send
plugin manager, not by putting the file on
> the disk. This will handle dependencies and so forth automatically.
>
> On Tue, Aug 2, 2016 at 11:10 AM rnara <rnaraha...@gmail.com >
> wrote:
>
>> Hi,
>>
>> I have added the latest "email extension plugi
You should install using the plugin manager, not by putting the file on the
disk. This will handle dependencies and so forth automatically.
On Tue, Aug 2, 2016 at 11:10 AM rnara <rnaraharise...@gmail.com> wrote:
> Hi,
>
> I have added the latest "email extension plugin"
Hi,
I have added the latest "email extension plugin" in the following location
on a Linux server in the Jenkins war file and restarted Jenkins, but it
doesn't show up in the installed plugins on Jenkins dash board. Please let
me know if I'm missing anything.
"WEB-INF/plugin
Hi,
Use following :
Where file path is relative to workspace.
Lets say you have file in $WORKSPACE/myfile, now to mail it use :
${FILE,path=myfile}
On Wednesday, May 20, 2015 at 1:48:43 PM UTC+5:30, Mohamed Sathack wrote:
Hi,
I have a summary report in the form of text file (say,
Look at the help for the content tokens. You probably want the FILE token.
On Wed, May 20, 2015, 01:18 Mohamed Sathack ssat...@gmail.com wrote:
Hi,
I have a summary report in the form of text file (say, summary.txt). This
fill will be hardly having few lines saying the overall status of my
Hi,
I have a summary report in the form of text file (say, summary.txt). This
fill will be hardly having few lines saying the overall status of my
execution. I have to use the files contents in the contents section of
extended email plugin. Can you please help?
Regards,
Mohamed Sathack
--
Hello,
I am using jenkins version 1.5803 and email extension plugin version
2.38.2. I am getting the below error while triggering the mail
.
+ exit 1
Build step 'Execute shell' marked build as failure
Email was triggered for: Always
Sending email for trigger: Always
ERROR: Could
jenkins version 1.5803 and email extension plugin version
2.38.2. I am getting the below error while triggering the mail
.
+ exit 1
Build step 'Execute shell' marked build as failure
Email was triggered for: Always
Sending email for trigger: Always
ERROR: Could not send email as a part
You probably want to upgrade email-ext, I believe this was fixed.
On Wed Feb 18 2015 at 3:16:32 AM Maneesh M P maneesh.po...@gmail.com
wrote:
Hello,
I am using jenkins version 1.5803 and email extension plugin version
2.38.2. I am getting the below error while triggering the mail
Version 2.36 seems to have fixed it.
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
Regards,
--
Ahmed Mubbashir Khan
I don't make Software, I make it better
http://about.me/mubbashir
On Wed, Oct 23, 2013 at 5:18 PM, Ulli Hafner
I'm not sure if this is related but it seems that 1.536 changed the JSON
binding (Jenkins core) which also breaks my plug-ins:
https://issues.jenkins-ci.org/browse/JENKINS-20199
Ulli
Am 22.10.2013 um 16:41 schrieb Slide slide.o@gmail.com:
Seems like something from the form is not making
Hi guys,
Today I had updated jenkins and it's plugin, after the update I am getting
some weird exception as soon as jenkins is done with scm This will only
happen if the build script of a job is updated.
After updating the build script I wasn't able to save the job (see below
the exception 1
I think we had this just yesterday, try removing and adding the email-ext
publisher, then make sure to add a trigger (e.g. 'Success').
On 22.10.2013, at 14:59, mubbashir mubbashi...@gmail.com wrote:
Hi guys,
Today I had updated jenkins and it's plugin, after the update I am getting
some
I tried the same after posting to the mailing list, didn't help :(
Regards,
--
Ahmed Mubbashir Khan
I don't make Software, I make it better
http://about.me/mubbashir
On Tue, Oct 22, 2013 at 6:09 PM, Daniel Beck m...@beckweb.net wrote:
I think we had this just
I tried the same after posting to the mailing list, didn't help :(
It actually went back to the same thing where I wasn't able to save the job
:(
On Tuesday, 22 October 2013 18:09:51 UTC+4, Daniel Beck wrote:
I think we had this just yesterday, try removing and adding the email-ext
Seems like something from the form is not making it through to the post
with the values for the DataBoundConstructor of the triggers.
project_triggers:[{stapler-class:,kind:},{stapler-class:
,kind:},{stapler-class:,kind:},{stapler-class
:,kind:},{stapler-class:,kind:}]
I'm not familiar enough
Hi,
as my developers keep asking about this I am re-sending my question.
If a long-running test job is started after 2 or more faster compiles went
through, I am only getting the changes for the last compile inside the
email (with email-extension plugin). What I would like to have instead
(with email-extension plugin). What I would like to have instead are
the changes in dependency if there has been more than 1 compile between the
test runs.
So I would be happy If I could use something like
${CHANGES_IN_DEPENDENCY_SINCE_LAST_SUCCESS, showPaths=true,
pathformat=%p}
which
question.
If a long-running test job is started after 2 or more faster compiles
went through, I am only getting the changes for the last compile inside the
email (with email-extension plugin). What I would like to have instead are
the changes in dependency if there has been more than 1 compile
Hi,
I have a compile job that runs continuously triggered by SCM which starts
about 40 or 50 test jobs after successful compilation.
I am printing the changes since last success (coming from the upstream
compile job) of a test job which is run after a compile job like this:
51 matches
Mail list logo