date:20201231

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-12-31 Thread Mohan

Manager credentials should be your domain LDAP Credentials. So it requires
the complete CN,OU details. To get that contact your domain administrators.

On Fri, 1 Jan 2021, 1:10 pm anilkumar panditi, 
wrote:

> Okay, can you help how to create manager credentials, also i am trying
> from the command (what is the user id need to give in this command)
>
> ldapsearch -x -h ad-ldap-server.com
>  -p 389 -D "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" -W
>
> Thanks,
> Anil
>
> On Friday, 1 January 2021 at 12:33:02 UTC+5:30 Mk wrote:
>
>> Hi Anil,
>>
>> Manager and manager password need to configured to validate the test
>> connection.
>>
>> On Fri, 1 Jan 2021, 12:29 pm anilkumar panditi, 
>> wrote:
>>
>>> Hi MK,
>>> i am getting ldap_bind: Invalid credentials (49)
>>>
>>> what are the credentials need to give here.
>>>
>>> Thanks,
>>> Anil
>>>
>>> On Saturday, 22 August 2020 at 10:00:55 UTC+5:30 Mk wrote:
>>>
 Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on
 jenkins master server terminal works. Below is the response.

 ldapsearch -x -h ad-ldap-server.com -p 389 -D
 "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b
 "OU=Users,OU=Division,OU=Team,DC=domain,DC=com"
 "(sAMAccountName=jenkins)" -W
 Enter LDAP Password:
 # extended LDIF
 #
 # LDAPv3
 # base  with scope
 subtree
 # filter: (sAMAccountName=jenkins)
 # requesting: ALL
 #

 # search result
 search: 2
 result: 0 Success

 # numResponses: 2
 # numEntries: 1

 Since i am getting reponse so seems i have permission to query the
 AD(LDAP) server.

 Also tried *Login name case sensitivity* & *Group name case
 sensitivity* - Both with *Case sensitive* & *Case insensitive *but
 still same result.



 On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff
 wrote:
>
> sounds like the user is valid but not a member of any groups. Is that
> possible?
>
>
>
> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>
>> Hi Team,
>>
>> I am trying to configure LDAP(AD) Authentication in our Jenkins,
>> Below is my configuration settings, But test LDAP connection is failing.
>>
>> Environment:-
>> Jenkins Version - 2.235.5(LTS)
>> LDAP Plugin - 1.24
>>
>>
>> Server - ldap://ad-ldap-server.com
>> root DN: DC=domain,DC=com
>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> User search filter: sAMAccountName={0}
>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Group search filter: (&(objectclass=group)(cn={0}))
>> Group membership
>>   Group membership filter -
>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Manager Password: password
>> Display Name LDAP attribute: displayname
>> Email Address LDAP attribute: mail
>>
>>
>> Error Message:-
>>
>> [image: 1.png]
>>
>> Please let me know what is missing in my configuration?. Any help
>> would be appreciated.
>>
> --
>>> 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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/b189583d-7246-41f2-89d3-0eef98e6c718n%40googlegroups.com
> 
> .
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2B4Hw5Y01ZD8Lo-QAiG8UxXdHjJ8kxuJ5Y6zokuxdKXEUEnpWQ%40mail.gmail.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-12-31 Thread anilkumar panditi

Okay, can you help how to create manager credentials, also i am trying from 
the command (what is the user id need to give in this command)

ldapsearch -x -h 
ad-ldap-server.com -p 389 -D 
"CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
"OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" -W  

Thanks,
Anil

On Friday, 1 January 2021 at 12:33:02 UTC+5:30 Mk wrote:

> Hi Anil,
>
> Manager and manager password need to configured to validate the test 
> connection.
>
> On Fri, 1 Jan 2021, 12:29 pm anilkumar panditi,  
> wrote:
>
>> Hi MK,
>> i am getting ldap_bind: Invalid credentials (49)
>>
>> what are the credentials need to give here.
>>
>> Thanks,
>> Anil
>>
>> On Saturday, 22 August 2020 at 10:00:55 UTC+5:30 Mk wrote:
>>
>>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on 
>>> jenkins master server terminal works. Below is the response. 
>>>
>>> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
>>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" 
>>> "(sAMAccountName=jenkins)" -W
>>> Enter LDAP Password:
>>> # extended LDIF
>>> #
>>> # LDAPv3
>>> # base  with scope subtree
>>> # filter: (sAMAccountName=jenkins)
>>> # requesting: ALL
>>> #
>>>
>>> # search result
>>> search: 2
>>> result: 0 Success
>>>
>>> # numResponses: 2
>>> # numEntries: 1
>>>
>>> Since i am getting reponse so seems i have permission to query the 
>>> AD(LDAP) server.
>>>
>>> Also tried *Login name case sensitivity* & *Group name case sensitivity* 
>>> - Both with *Case sensitive* & *Case insensitive *but still same 
>>> result. 
>>>
>>>
>>>
>>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff 
>>> wrote:

 sounds like the user is valid but not a member of any groups. Is that 
 possible? 



 On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:

> Hi Team,
>
> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below 
> is my configuration settings, But test LDAP connection is failing.
>
> Environment:-
> Jenkins Version - 2.235.5(LTS)
> LDAP Plugin - 1.24
>
>
> Server - ldap://ad-ldap-server.com
> root DN: DC=domain,DC=com
> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> User search filter: sAMAccountName={0}
> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> Group search filter: (&(objectclass=group)(cn={0}))
> Group membership
>   Group membership filter - 
> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> Manager Password: password
> Display Name LDAP attribute: displayname
> Email Address LDAP attribute: mail
>
>
> Error Message:-
>
> [image: 1.png]
>
> Please let me know what is missing in my configuration?. Any help 
> would be appreciated.
>
 -- 
>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b189583d-7246-41f2-89d3-0eef98e6c718n%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-12-31 Thread Mohan

Hi Anil,

Manager and manager password need to configured to validate the test
connection.

On Fri, 1 Jan 2021, 12:29 pm anilkumar panditi, 
wrote:

> Hi MK,
> i am getting ldap_bind: Invalid credentials (49)
>
> what are the credentials need to give here.
>
> Thanks,
> Anil
>
> On Saturday, 22 August 2020 at 10:00:55 UTC+5:30 Mk wrote:
>
>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on
>> jenkins master server terminal works. Below is the response.
>>
>> ldapsearch -x -h ad-ldap-server.com -p 389 -D
>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b
>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com"
>> "(sAMAccountName=jenkins)" -W
>> Enter LDAP Password:
>> # extended LDIF
>> #
>> # LDAPv3
>> # base  with scope subtree
>> # filter: (sAMAccountName=jenkins)
>> # requesting: ALL
>> #
>>
>> # search result
>> search: 2
>> result: 0 Success
>>
>> # numResponses: 2
>> # numEntries: 1
>>
>> Since i am getting reponse so seems i have permission to query the
>> AD(LDAP) server.
>>
>> Also tried *Login name case sensitivity* & *Group name case sensitivity*
>> - Both with *Case sensitive* & *Case insensitive *but still same result.
>>
>>
>>
>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff wrote:
>>>
>>> sounds like the user is valid but not a member of any groups. Is that
>>> possible?
>>>
>>>
>>>
>>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>>
 Hi Team,

 I am trying to configure LDAP(AD) Authentication in our Jenkins, Below
 is my configuration settings, But test LDAP connection is failing.

 Environment:-
 Jenkins Version - 2.235.5(LTS)
 LDAP Plugin - 1.24


 Server - ldap://ad-ldap-server.com
 root DN: DC=domain,DC=com
 User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
 User search filter: sAMAccountName={0}
 Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
 Group search filter: (&(objectclass=group)(cn={0}))
 Group membership
   Group membership filter -
 (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
 Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
 Manager Password: password
 Display Name LDAP attribute: displayname
 Email Address LDAP attribute: mail


 Error Message:-

 [image: 1.png]

 Please let me know what is missing in my configuration?. Any help would
 be appreciated.

>>> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com
> 
> .
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2B4Hw5ZUfzJqu7%2BreizETtqv_Opr33TPpLxhrLD1eFmTo6Hv9Q%40mail.gmail.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-12-31 Thread anilkumar panditi

Hi MK,
i am getting ldap_bind: Invalid credentials (49)

what are the credentials need to give here.

Thanks,
Anil

On Saturday, 22 August 2020 at 10:00:55 UTC+5:30 Mk wrote:

> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on jenkins 
> master server terminal works. Below is the response. 
>
> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" 
> -W
> Enter LDAP Password:
> # extended LDIF
> #
> # LDAPv3
> # base  with scope subtree
> # filter: (sAMAccountName=jenkins)
> # requesting: ALL
> #
>
> # search result
> search: 2
> result: 0 Success
>
> # numResponses: 2
> # numEntries: 1
>
> Since i am getting reponse so seems i have permission to query the 
> AD(LDAP) server.
>
> Also tried *Login name case sensitivity* & *Group name case sensitivity* 
> - Both with *Case sensitive* & *Case insensitive *but still same result. 
>
>
>
> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff wrote:
>>
>> sounds like the user is valid but not a member of any groups. Is that 
>> possible? 
>>
>>
>>
>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>
>>> Hi Team,
>>>
>>> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below 
>>> is my configuration settings, But test LDAP connection is failing.
>>>
>>> Environment:-
>>> Jenkins Version - 2.235.5(LTS)
>>> LDAP Plugin - 1.24
>>>
>>>
>>> Server - ldap://ad-ldap-server.com
>>> root DN: DC=domain,DC=com
>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> User search filter: sAMAccountName={0}
>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Group search filter: (&(objectclass=group)(cn={0}))
>>> Group membership
>>>   Group membership filter - 
>>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Manager Password: password
>>> Display Name LDAP attribute: displayname
>>> Email Address LDAP attribute: mail
>>>
>>>
>>> Error Message:-
>>>
>>> [image: 1.png]
>>>
>>> Please let me know what is missing in my configuration?. Any help would 
>>> be appreciated.
>>>
>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ff6057a3-0c96-48d9-ae83-7c8cfe234fe9n%40googlegroups.com.

Gracefully ignoring unavailable agents

2020-12-31 Thread 'Mark Raynsford' via Jenkins Users

Hello!

Let's say I'm using a declarative pipeline setup like this:

~~
#!groovy

pipeline {

  agent none

  stages {
stage('Build') {
  parallel {
stage('Build Linux') {
  stages {
stage('Build:linux:openjdk-11-hotspot') {
  agent {
label 'linux'
  }
  ...
}
stage('Build:linux:openjdk-15-hotspot') {
  agent {
label 'linux'
  }
  ...
}
  }
}

stage('Build Windows') {
  stages {
stage('Build:windows:openjdk-11-hotspot') {
  agent {
label 'windows'
  }
  ...
}
stage('Build:windows:openjdk-15-hotspot') {
  agent {
label 'windows'
  }
  ...
}
  }
}
  }
}
  }
}
~~

As you can see, I use labels to select agents to run builds on specific
operating systems and with a fixed set of specific JDK versions. This
all works fine. However: With my current hardware setup, the Windows
node is _not_ going to be online 24/7 (the Linux node is always
available).

Is there a way I can adapt the above pipeline to basically say "If
there's a Windows node online, run the stages, otherwise trivially
succeed"? Right now, if no Windows node is available, the pipeline will
hang until either one becomes available or the entire job times out.

-- 
Mark Raynsford | https://www.io7m.com

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20201231212628.447a21b5%40sunflower.int.arc7.info.


pgphJWP5Tswnu.pgp
Description: OpenPGP digital signature

Re: Jenkins master/slave ping timeout settings: disable or increase?

2020-12-31 Thread jiga...@gmail.com



On Wednesday, April 15, 2020 at 2:06:19 AM UTC-4 monger_39 wrote:

> Hey Jeff,
> looks indeed like the 'standard' type of problems. Unfortunately in our 
> network, I do not have the
> privileges to do anything much.  Not that that would help much, since I'm 
> only a simple SW engineer,
> not a network specialist.
> The tip to try another agent connection is a good one though. Will try 
> that.
>
> I have been running on JNLP for a while. Is it going to be deprecated? 
Should I prepare to move to SSH?
 

> thx again, David
>
> On Tuesday, April 14, 2020, 07:52:18 PM GMT+2, Jeff Thompson <
> jtho...@cloudbees.com> wrote: 
>
>
> Unfortunately, it's really hard to say. Possibilities include resource 
> contention, such as CPU or networking, anything in the middle, such as load 
> balancers, firewalls, etc., network or system configuration. I heard of one 
> a while back that ended up being connected to IP table definition. Can't 
> remember if that was related to docker containers or full VMs. I've heard 
> that there have been some common problems in some VM environments, but I 
> don't know what environments or issues specifically. Maybe VMotion. Maybe 
> the network gets overloaded, especially between VMs. Or interactions 
> between loads on different VMs. I'm not as familiar with the current state, 
> but in the past in other environments I have seen more interference between 
> VMs than expected.
>
> It comes down to standard troubleshooting sorts of behavior. Try to catch 
> the problem. Gather information about different occurrences. Try to isolate 
> any commonalities. Isolate a system for reproduction.
>
> You could try a different type of agent, such as an SSH Agent. The 
> behavior might be different. I've heard recently that Microsoft's SSHD 
> implementation works well.
>
> Good luck on troubleshooting
>
> Jeff
> On 4/14/20 8:31 AM, 'monger_39' via Jenkins Users wrote:
>
> Hi Jeff,
> thx. Last week I disabled the ping-thread on master and slaves by setting 
> the interval to '-1'.
> Unfortunately, over the weekend, again one of the slaves (even though the 
> jobs kept on running),
> went into 'offline' mode.  It seems indeed that this does not solve the 
> issue. Or, iow I think it means
> that the disconnect was not caused by the ping-thread(s) timing out. 
>
> Which puts me to the challenge to figure out what could be this 'external 
> someting' that you mention
> that would break the remoting. And I honestly have no idea how to tackle 
> that yet.
> The master, as well as the slave are Windows server VM's running 6 
> executor slots each. The
> tests we are running heavily use TCP communication. 
>
> Any idea how to tackle this ?
>
> thx, M.
> On Thursday, April 9, 2020, 10:53:48 PM GMT+2, Jeff Thompson 
>  wrote: 
>
>
> On 4/7/20 11:46 PM, 'monger_39' via Jenkins Users wrote:
>
> Hi,
> in my Jenkins I am regularly facing master/slave connection drops with a
> message like:
>
> hudson.remoting.ChannelClosedException: Channel "unknown": Remote
> call on JNLP4-connect connection from IP/IP:58344 failed.
> The channel is closing down or has closed down.
>
> Usually these are caused by something external to the Remoting 
> communication protocol. Most often by something in the system or networking 
> environment. Sometimes by some bad interaction between plugins that ends up 
> impacting the channel.
>
> Your best approach is to figure out where these disconnects originate and 
> resolve the issue.
>
>
> I have seen a lot of bug-reports on this. For most, a workaround is
> advised by disabling the Ping-Thread through setting:
>
> You should be cautious about changing the ping settings or disabling it 
> entirely. It can cause some weird and unexpected behaviors. If you do 
> change the settings, I recommend you change one thing at a time and 
> evaluate the results. If it doesn't make any difference, restore it to its 
> default setting. 
>
> And, is there also a slave setting for the timeoutvalue?
>
> It depends on how you launch the agent. Remoting system properties are 
> described at 
> https://github.com/jenkinsci/remoting/blob/master/docs/configuration.md
>
> (naming for all these settings does not look to be very consistent...)
>
> Unfortunately, that's the case.
>
> Jeff Thompson
>
> -- 
> 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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
>
> https://groups.google.com/d/msgid/jenkinsci-users/ab43b555-176c-4834-e125-fb66ff612f4d%40cloudbees.com
>  
> 
>  
> .
> -- 
> 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,

Re: Jenkins Integration with LDAP - Testing Connection Fails

Re: Jenkins Integration with LDAP - Testing Connection Fails

Re: Jenkins Integration with LDAP - Testing Connection Fails

Re: Jenkins Integration with LDAP - Testing Connection Fails

Gracefully ignoring unavailable agents

Re: Jenkins master/slave ping timeout settings: disable or increase?

6 matches

Site Navigation

Mail list logo

Footer information