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
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
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
valid email address attribute?
>
> On Thu, Jun 4, 2020 at 10:57 AM Mario Jauvin > wrote:
>
>> I noticed that the error comes from
>> ActiveDirectoryMailAddressResolverImpl in the active_directory plugin. Any
>> suggestion? Is this a problem with the plugin or with th
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
t; like you would need the LDAP plugin installed and configured, is that the
> case?
>
> On Thu, Jun 4, 2020 at 8:25 AM Mario Jauvin > wrote:
>
>> Is there some diagnostics or debugging I can turn on to troubleshoot this?
>>
>> On Thursday, June 4, 2020 at 9:38:14 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 organi
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
wrote:
>
> 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 u
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
Would there be a way to create a groovy variable named agentObject that
either contains the object {label "$agentLabel"} or the object any provided
by the pipeline namespace and use a syntax like: agent $agentObject?
On Monday, December 30, 2019 at 8:53:12 AM UTC-5, Mario Ja
>
> This seems to be the only way that I can get it working but it requires
>> repeating the pipeline twice which in my case is a complicated one:
>>
>
def call(String buildType, String agentLabel=null) {
if ("versionBranch".equals(buildType)) {
if (agentLabel==null) {
pipeline {
ot;${agentLabel}"}
}
rest of the pipeline
}
}
On Friday, December 27, 2019 at 4:59:13 PM UTC-5, Mario Jauvin wrote:
> I currently use a shared library with a call method. I would like to
> specify an argument to either use the agent any or agent {label
> 'some-label'}.
>
> I ha
I currently use a shared library with a call method. I would like to
specify an argument to either use the agent any or agent {label
'some-label'}.
I have the call method as such:
def call(String buildType, String agentLabel=null) {
if ("versionBranch".equals(buildType)) {
}
--
You
What is the purpose of this build step and how to use it? Are there
examples? The documentation Use a tool from a predefined Tool Installation
is not very helpful.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
By "Google has not provided any insight" I meant that google search did not
return any useful information.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I tried in many different manner to get this working using Blue Ocean and
its pipeline editor and I was unable. I looked at the example
https://jenkins.io/doc/tutorials/build-a-java-app-with-maven/ but this only
works using two docker Linux containers, one running Jenkins and the other
one
21 matches
Mail list logo
