date:20200901

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-09-01 Thread Mk

I have fixed it. Each time when we change/update the *"Display Name LDAP 
attribute" *value in LDAP configuration section, We need to delete the user 
from people category and need to login. Post that it displays the 
configured settings.

On Wednesday, September 2, 2020 at 9:57:31 AM UTC+5:30, Mk wrote:
>
> Team, Is it possible to display only *First name + Sur-name* in Jenkins?
>
>
> On Friday, August 28, 2020 at 9:56:39 AM UTC+5:30, Mk wrote:
>>
>> Dear Team,
>>
>> Now our LDAP Authentication working fine. I have question regarding 
>> "*Display 
>> Name LDAP attribute*: *displayname*" i have configured like this and for 
>> all logged in users, The display name shown as like below which is too 
>> lengthy/long.
>>
>> First-Name/Sur-Name/Team-Name/Location/Title/Company-Name
>>
>> Would like to display only *First-Name + Sur-Name*. For this i tried to 
>> change Display Name LDAP attribute: with name such as *givenName, cn* & *sn 
>> *but none of them are worked. So is it possible to display only *First 
>> name + Sur-name* in Jenkins for logged-in users?
>>
>> On Sunday, August 23, 2020 at 10:37:42 AM UTC+5:30, Mk wrote:
>>>
>>> Hi Jeremy,
>>>
>>> Even LDAP Login slowness issue also resolved with below configuration.
>>>
>>> Group membership filter - (memberOf={0})
>>>
>>> Enable cache
>>> Cache size - 200
>>> Cache TTL - 30min
>>>
>>> Now everything working as excepted, But would like to know that 
>>> currently i am running* root DN* as *empty *and *enabled - Allow blank 
>>> rootDN* in plugin section. Is this is fine?
>>>
>>> On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:

 Hi Jeremy,

 I have tried by keeping the *root DN* as *empty *and enabled the* tick 
 mark - Allow blank rootDN. *now my test connection is successful but 
 took around *4mins* to show the successful result. Below is the 
 configuration used.

 root DN - Allow blank rootDN

 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

 Now how to figureout the login performace issue? Another thing keeping 
 the *root DN* empty does not an issue?


 On Saturday, August 22, 2020 at 10:00:55 AM 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]
>>>

Re: Unable to Update Jenkins and Plugin

2020-09-01 Thread Richard Bywater

Are you running in a corporate environment that uses a proxy to talk to the
Internet? If so then you'll need to ensure that the certificate used by the
proxy (assuming it intercepts TLS traffic) is loaded in the "cacerts" file
for the given version of Java. Unfortunately I'm not sure where that
resides on a Windows instance.

Richard.

On Wed, 2 Sep 2020 at 16:44, cmc...@gmail.com  wrote:

> master is running current JRE 8
> java.version
> 1.8.0_261
>
> I was able to upgrade from jenkins-2.222.3 to jenkins-2.235.1 at 06/30/20.
> I am puzzled by this error.
>
> On Tuesday, September 1, 2020 at 6:54:23 PM UTC-7 Mark Waite wrote:
>
>> That may indicate that the Java installation used by your Jenkins on
>> WIndows does not recognize the SSL certificates that Let's Encrypt provides
>> for the Jenkins update center.
>>
>> Check the Java version from the "System Information" page in "Manage
>> Jenkins".  Java 8u262 is the most recent version of Java 8.  Java 11.0.8 is
>> the most recent version of Java 11.  If you're not running one of those
>> versions, download and install a version of AdoptOpenJDK for Windows and
>> modify the Jenkins configuration to use that new Java installation.
>>
>> On Tue, Sep 1, 2020 at 6:03 PM cmc...@gmail.com  wrote:
>>
>>> I am running Jenkins 2.235.1 on Windows.  I am not able to Update
>>> Jenkins and Plugin failed to update.  I have tried to installed self sign
>>> SSL Cert and does not solve the issue.  What is the cause and how to fix?
>>>
>>>
>>>
>>>  Failure -
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>>> find valid certification path to requested target at
>>> sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at
>>> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown
>>> Source) at java.security.cert.CertPathBuilder.build(Unknown Source) Caused:
>>> sun.security.validator.ValidatorException: PKIX path building failed at
>>> sun.security.validator.PKIXValidator.doBuild(Unknown Source) at
>>> sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at
>>> sun.security.validator.Validator.validate(Unknown Source) at
>>> sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at
>>> sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at
>>> sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
>>> Caused: javax.net.ssl.SSLHandshakeException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target at
>>> sun.security.ssl.Alert.createSSLException(Unknown Source) at
>>> sun.security.ssl.TransportContext.fatal(Unknown Source) at
>>> sun.security.ssl.TransportContext.fatal(Unknown Source) at
>>> sun.security.ssl.TransportContext.fatal(Unknown Source) at
>>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(Unknown
>>> Source) at
>>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(Unknown
>>> Source) at
>>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(Unknown
>>> Source) at sun.security.ssl.SSLHandshake.consume(Unknown Source) at
>>> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at
>>> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at
>>> sun.security.ssl.TransportContext.dispatch(Unknown Source) at
>>> sun.security.ssl.SSLTransport.decode(Unknown Source) at
>>> sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at
>>> sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at
>>> sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
>>>
>>> --
>>> 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/0d0c3c60-741e-4ef9-a362-3fed70c8bf7fn%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/01ce2a4c-d423-4a55-ac2a-e9e71445df25n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.

Re: Unable to Update Jenkins and Plugin

2020-09-01 Thread cmc...@gmail.com

master is running current JRE 8
java.version
1.8.0_261  

I was able to upgrade from jenkins-2.222.3 to jenkins-2.235.1 at 06/30/20.
I am puzzled by this error.

On Tuesday, September 1, 2020 at 6:54:23 PM UTC-7 Mark Waite wrote:

> That may indicate that the Java installation used by your Jenkins on 
> WIndows does not recognize the SSL certificates that Let's Encrypt provides 
> for the Jenkins update center.
>
> Check the Java version from the "System Information" page in "Manage 
> Jenkins".  Java 8u262 is the most recent version of Java 8.  Java 11.0.8 is 
> the most recent version of Java 11.  If you're not running one of those 
> versions, download and install a version of AdoptOpenJDK for Windows and 
> modify the Jenkins configuration to use that new Java installation.
>
> On Tue, Sep 1, 2020 at 6:03 PM cmc...@gmail.com  wrote:
>
>> I am running Jenkins 2.235.1 on Windows.  I am not able to Update Jenkins 
>> and Plugin failed to update.  I have tried to installed self sign SSL Cert 
>> and does not solve the issue.  What is the cause and how to fix?
>>
>>
>>
>>  Failure -
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to 
>> find valid certification path to requested target at 
>> sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at 
>> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown 
>> Source) at java.security.cert.CertPathBuilder.build(Unknown Source) Caused: 
>> sun.security.validator.ValidatorException: PKIX path building failed at 
>> sun.security.validator.PKIXValidator.doBuild(Unknown Source) at 
>> sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at 
>> sun.security.validator.Validator.validate(Unknown Source) at 
>> sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at 
>> sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at 
>> sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) 
>> Caused: javax.net.ssl.SSLHandshakeException: PKIX path building failed: 
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
>> valid certification path to requested target at 
>> sun.security.ssl.Alert.createSSLException(Unknown Source) at 
>> sun.security.ssl.TransportContext.fatal(Unknown Source) at 
>> sun.security.ssl.TransportContext.fatal(Unknown Source) at 
>> sun.security.ssl.TransportContext.fatal(Unknown Source) at 
>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(Unknown
>>  
>> Source) at 
>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(Unknown
>>  
>> Source) at 
>> sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(Unknown 
>> Source) at sun.security.ssl.SSLHandshake.consume(Unknown Source) at 
>> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at 
>> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at 
>> sun.security.ssl.TransportContext.dispatch(Unknown Source) at 
>> sun.security.ssl.SSLTransport.decode(Unknown Source) at 
>> sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at 
>> sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at 
>> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at 
>> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at 
>> sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)  
>>
>> -- 
>> 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/0d0c3c60-741e-4ef9-a362-3fed70c8bf7fn%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/01ce2a4c-d423-4a55-ac2a-e9e71445df25n%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-09-01 Thread Mk

Team, Is it possible to display only *First name + Sur-name* in Jenkins?


On Friday, August 28, 2020 at 9:56:39 AM UTC+5:30, Mk wrote:
>
> Dear Team,
>
> Now our LDAP Authentication working fine. I have question regarding "*Display 
> Name LDAP attribute*: *displayname*" i have configured like this and for 
> all logged in users, The display name shown as like below which is too 
> lengthy/long.
>
> First-Name/Sur-Name/Team-Name/Location/Title/Company-Name
>
> Would like to display only *First-Name + Sur-Name*. For this i tried to 
> change Display Name LDAP attribute: with name such as *givenName, cn* & *sn 
> *but none of them are worked. So is it possible to display only *First 
> name + Sur-name* in Jenkins for logged-in users?
>
> On Sunday, August 23, 2020 at 10:37:42 AM UTC+5:30, Mk wrote:
>>
>> Hi Jeremy,
>>
>> Even LDAP Login slowness issue also resolved with below configuration.
>>
>> Group membership filter - (memberOf={0})
>>
>> Enable cache
>> Cache size - 200
>> Cache TTL - 30min
>>
>> Now everything working as excepted, But would like to know that currently 
>> i am running* root DN* as *empty *and *enabled - Allow blank rootDN* in 
>> plugin section. Is this is fine?
>>
>> On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:
>>>
>>> Hi Jeremy,
>>>
>>> I have tried by keeping the *root DN* as *empty *and enabled the* tick 
>>> mark - Allow blank rootDN. *now my test connection is successful but 
>>> took around *4mins* to show the successful result. Below is the 
>>> configuration used.
>>>
>>> root DN - Allow blank rootDN
>>>
>>> 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
>>>
>>> Now how to figureout the login performace issue? Another thing keeping 
>>> the *root DN* empty does not an issue?
>>>
>>>
>>> On Saturday, August 22, 2020 at 10:00:55 AM 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

Re: Unable to Update Jenkins and Plugin

2020-09-01 Thread Mark Waite

That may indicate that the Java installation used by your Jenkins on
WIndows does not recognize the SSL certificates that Let's Encrypt provides
for the Jenkins update center.

Check the Java version from the "System Information" page in "Manage
Jenkins".  Java 8u262 is the most recent version of Java 8.  Java 11.0.8 is
the most recent version of Java 11.  If you're not running one of those
versions, download and install a version of AdoptOpenJDK for Windows and
modify the Jenkins configuration to use that new Java installation.

On Tue, Sep 1, 2020 at 6:03 PM cmc...@gmail.com  wrote:

> I am running Jenkins 2.235.1 on Windows.  I am not able to Update Jenkins
> and Plugin failed to update.  I have tried to installed self sign SSL Cert
> and does not solve the issue.  What is the cause and how to fix?
>
>
>
>  Failure -
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target at
> sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at
> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown
> Source) at java.security.cert.CertPathBuilder.build(Unknown Source) Caused:
> sun.security.validator.ValidatorException: PKIX path building failed at
> sun.security.validator.PKIXValidator.doBuild(Unknown Source) at
> sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at
> sun.security.validator.Validator.validate(Unknown Source) at
> sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at
> sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at
> sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
> Caused: javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target at
> sun.security.ssl.Alert.createSSLException(Unknown Source) at
> sun.security.ssl.TransportContext.fatal(Unknown Source) at
> sun.security.ssl.TransportContext.fatal(Unknown Source) at
> sun.security.ssl.TransportContext.fatal(Unknown Source) at
> sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(Unknown
> Source) at
> sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(Unknown
> Source) at
> sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(Unknown
> Source) at sun.security.ssl.SSLHandshake.consume(Unknown Source) at
> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at
> sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at
> sun.security.ssl.TransportContext.dispatch(Unknown Source) at
> sun.security.ssl.SSLTransport.decode(Unknown Source) at
> sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at
> sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at
> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at
> sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at
> sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
>
> --
> 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/0d0c3c60-741e-4ef9-a362-3fed70c8bf7fn%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/CAO49JtErNU_wkjWw6GNgeuy2-vM8Y6NeW081rH0SMOTUSipS%3Dw%40mail.gmail.com.

Unable to Update Jenkins and Plugin

2020-09-01 Thread cmc...@gmail.com

I am running Jenkins 2.235.1 on Windows.  I am not able to Update Jenkins 
and Plugin failed to update.  I have tried to installed self sign SSL Cert 
and does not solve the issue.  What is the cause and how to fix?



 Failure -
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path to requested target at 
sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at 
sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown 
Source) at java.security.cert.CertPathBuilder.build(Unknown Source) Caused: 
sun.security.validator.ValidatorException: PKIX path building failed at 
sun.security.validator.PKIXValidator.doBuild(Unknown Source) at 
sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at 
sun.security.validator.Validator.validate(Unknown Source) at 
sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at 
sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at 
sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) 
Caused: javax.net.ssl.SSLHandshakeException: PKIX path building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path to requested target at 
sun.security.ssl.Alert.createSSLException(Unknown Source) at 
sun.security.ssl.TransportContext.fatal(Unknown Source) at 
sun.security.ssl.TransportContext.fatal(Unknown Source) at 
sun.security.ssl.TransportContext.fatal(Unknown Source) at 
sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(Unknown
 
Source) at 
sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(Unknown
 
Source) at 
sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(Unknown 
Source) at sun.security.ssl.SSLHandshake.consume(Unknown Source) at 
sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at 
sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at 
sun.security.ssl.TransportContext.dispatch(Unknown Source) at 
sun.security.ssl.SSLTransport.decode(Unknown Source) at 
sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at 
sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at 
sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at 
sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at 
sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)  

-- 
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/0d0c3c60-741e-4ef9-a362-3fed70c8bf7fn%40googlegroups.com.

convert declarative pipeline stage to scripted pipeline

2020-09-01 Thread Majid



I already used the following declarative cleanup pipeline for Jenkin, 
according to the feature of my code, I have to convert into the scripted 
pipeline, how I can convert it to the scripted pipeline?
stage ('Cleanup Feature Releases') {
 steps {
 script {
 envParameters = Utils.getEnvParameters("${TARGET_ENV}")
  withKubeConfig([credentialsId: envParameters.K8S_TOKEN,
 serverUrl: 
envParameters.K8S_API_SERVER,
 contextName: CONTEXT_NAME
]) {
sh "Running on ${params.OVERRIDE_NAMESPACE}"
 }
  }
 }
 post {
 failure {
cleanUpNotification("FAILURE", params.DRY_RUN)
  }
  aborted {
 cleanUpNotification("ABORTED", params.DRY_RUN)
   }
   success {
  cleanUpNotification("SUCCESS", params.DRY_RUN)
   }
}
}

-- 
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/349c3bc3-d9db-48a0-afca-2faeefe13fa1n%40googlegroups.com.

Re: one downstream with multiple upstreams(all upstreams should be success)

2020-09-01 Thread chenna kesavulu

Hi Gianluca,

I can't trigger Job D directly from Job A. Actually in my project we are
running integration tests in Job B and UI tests in Job C. So if both the
builds are green then only  i can merge the code to master in Job D. But
thanks for your answer I will try it.

Thanks,
Keshav.


On Wed, Sep 2, 2020 at 1:26 AM Gianluca  wrote:

> Hi,
> why not triggering Job D directly from job A ? In this way, if you put
> that in a stage after job B and job C is triggered ... it will only be
> triggered if both succedded:
>
> stage("Run B and C") {
>   steps {
> parallel(
>   "job B": { buildJob ... },
>   "job C:" { build Job ... },
> }
>
> stage("Run D") {
>   steps {
>// this will run only if both Job B and C succeed
> buildJob
>   }
> }
>
> Cheers,
> Gianluca.
>
> Il giorno martedì 1 settembre 2020 alle 19:52:49 UTC+1 chenna keshav ha
> scritto:
>
>> Hi,
>>
>> i have stuck with a small issue... i have a job A which triggers job B
>> and job C. for job B and job C downstream job is job D i need this job
>> D is to be triggered when job B and job C both are success. i have tried
>> with "Build after other projects are build" with "trigger only if build is
>> stable" option. its not working for me... the job is getting triggered even
>> one of jobs is success. can some one please help me on this..
>>
>> Thanks,
>> Keshav.
>>
> --
> 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/d4839902-97c8-4eb5-baa2-a080a400cfdbn%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/CABgMPaGxNu_fgFgFytBvZ72vZBKoLBqwj7XEN%3DzaQBMGW1%2BKYw%40mail.gmail.com.

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Hi, for some obscure reason, the machine Window update were not totally up to 
date. Performing the all the update seem to have fix the issue. So it seem like 
old Windows 10 build aren’t working. Sorry for all the noise. Did try with and 
without the anti-virus, no difference. There was nothing meaningful into the 
master ssh.

Sorry could not test the manual ssh command since the machine was already into 
the process to perform the windows update…

Hope this help others, if they face the issue.

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Ivan Fernandez Calvo
Sent: September 1, 2020 3:17 PM
To: Jenkins Users 
Subject: Re: Windows client ssh connection error

>Does it require the user to be admin?

no, a regular user should work if has access to the workdir

>Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850

this issue has a different stack trace and fails in another place.
The issue here happens after the SSH connection when the remoting process tries 
to read from the stdin, there is nothing to read, and the remoting process 
exits.

Do you have an antivirus enabled in that machine?

Did you check the SSHD service logs on your agent? try to increase the 
verbosity by setting LogLevel VERBOSE or LogLevel DEBUG1 on your 
/etc/ssh/sshd_config file and see 
Logging_and_Troubleshooting
Could you try to run the remoting commands manually from the Jenkins instance 
and see if the remoting process stars?
ssh user@jenkins_agent "cd c:\JenkinsSlave && C:\Java\1_8_0_261\bin\java  -jar 
remoting.jar -workDir c:\JenkinsSlave -jar-cache 
c:\JenkinsSlave\remoting\jarCache"


El martes, 1 de septiembre de 2020 a las 20:26:20 UTC+2, Jérôme Godbout 
escribió:
Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850

From: jenkins...@googlegroups.com  On Behalf Of 
Jérôme Godbout
Sent: September 1, 2020 2:12 PM
To: jenkins...@googlegroups.com
Subject: RE: Windows client ssh connection error

Did try without the firewall and it doesn’t work either, !?!? Anyone got an 
idea what it is actually doing that might not work?!? Both machine are on the 
same network, no ip conflict. If I delete the remoting.jar and the folders into 
c:\JenkinsSlave it get created again, so the connection is happening and it can 
transfer the file.

From: jenkins...@googlegroups.com  On Behalf Of 
Jérôme Godbout
Sent: September 1, 2020 2:05 PM
To: jenkins...@googlegroups.com
Subject: RE: Windows client ssh connection error

Hi,

Is there any special requirements? (ssh does work from both Linux and Windows 
to this machine, also from the Jenkins master user account too). Seem like 
starting the slave fails, anything to do with firewall or something like that?

here the node that work (Windows 10 64 bits):
[09/01/20 09:26:41] [SSH] Checking java version of 
C:\Java\jdk1.8.0_261\/bin/java
[09/01/20 09:26:42] [SSH] C:\Java\jdk1.8.0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 09:26:42] [SSH] Starting sftp client.
[09/01/20 09:26:42] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 09:26:55] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\jdk1.8.0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
Sep 01, 2020 9:26:56 AM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 9:26:57 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 4.3
This is a Windows agent
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SlaveListener call
INFO: Slave-status listener starting
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SocketHTTPListener 
waitForConnection
INFO: Slave-status listener ready on port 3141
[StartupTrigger] - Scanning jobs for node WindowsJG
Agent successfully connected and online


The one that doesn’t work (Windows 10 64 bits also, using the same Java jdk 
version):

[09/01/20 14:00:16] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java

[09/01/20 14:00:16] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.

[09/01/20 14:00:16] [SSH] Starting sftp client.

[09/01/20 14:00:16] [SSH] Copying latest remoting.jar...

[09/01/20 14:00:19] [SSH] Copied 1,522,833 bytes.

Expanded the channel window size to 4MB

[09/01/20 14:00:19] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache

<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020

Re: one downstream with multiple upstreams(all upstreams should be success)

2020-09-01 Thread Gianluca

Hi,
why not triggering Job D directly from job A ? In this way, if you put that 
in a stage after job B and job C is triggered ... it will only be triggered 
if both succedded:

stage("Run B and C") {
  steps {
parallel(
  "job B": { buildJob ... },
  "job C:" { build Job ... },
}

stage("Run D") {
  steps {
   // this will run only if both Job B and C succeed
buildJob
  }
}

Cheers,
Gianluca.

Il giorno martedì 1 settembre 2020 alle 19:52:49 UTC+1 chenna keshav ha 
scritto:

> Hi,
>
> i have stuck with a small issue... i have a job A which triggers job B and 
> job C. for job B and job C downstream job is job D i need this job D is 
> to be triggered when job B and job C both are success. i have tried with 
> "Build after other projects are build" with "trigger only if build is 
> stable" option. its not working for me... the job is getting triggered even 
> one of jobs is success. can some one please help me on this..
>
> Thanks,
> Keshav.
>

-- 
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/d4839902-97c8-4eb5-baa2-a080a400cfdbn%40googlegroups.com.

Re: Windows client ssh connection error

2020-09-01 Thread Ivan Fernandez Calvo

>Does it require the user to be admin?

no, a regular user should work if has access to the workdir 

>Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850

this issue has a different stack trace and fails in another place. 

The issue here happens after the SSH connection when the remoting process 
tries to read from the stdin, there is nothing to read, and the remoting 
process exits. 

Do you have an antivirus enabled in that machine?

Did you check the SSHD service logs on your agent? try to increase the 
verbosity by setting LogLevel VERBOSE or LogLevel DEBUG1 on your 
/etc/ssh/sshd_config file and see Logging_and_Troubleshooting 

Could you try to run the remoting commands manually from the Jenkins 
instance and see if the remoting process stars? 
ssh user@jenkins_agent "cd c:\JenkinsSlave && C:\Java\1_8_0_261\bin\java  
-jar remoting.jar -workDir c:\JenkinsSlave -jar-cache 
c:\JenkinsSlave\remoting\jarCache"


El martes, 1 de septiembre de 2020 a las 20:26:20 UTC+2, Jérôme Godbout 
escribió:

> Maybe this unresolved issue is still there!?
>
> https://issues.jenkins-ci.org/browse/JENKINS-48850
>
>  
>
> *From:* jenkins...@googlegroups.com  *On 
> Behalf Of *Jérôme Godbout
> *Sent:* September 1, 2020 2:12 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* RE: Windows client ssh connection error
>
>  
>
> Did try without the firewall and it doesn’t work either, !?!? Anyone got 
> an idea what it is actually doing that might not work?!? Both machine are 
> on the same network, no ip conflict. If I delete the remoting.jar and the 
> folders into c:\JenkinsSlave it get created again, so the connection is 
> happening and it can transfer the file.
>
>  
>
> *From:* jenkins...@googlegroups.com  *On 
> Behalf Of *Jérôme Godbout
> *Sent:* September 1, 2020 2:05 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* RE: Windows client ssh connection error
>
>  
>
> Hi,
>
>  
>
> Is there any special requirements? (ssh does work from both Linux and 
> Windows to this machine, also from the Jenkins master user account too). 
> Seem like starting the slave fails, anything to do with firewall or 
> something like that?
>
>  
>
> here the node that work (Windows 10 64 bits):
>
> [09/01/20 09:26:41] [SSH] Checking java version of 
> C:\Java\jdk1.8.0_261\/bin/java
>
> [09/01/20 09:26:42] [SSH] C:\Java\jdk1.8.0_261\/bin/java -version returned 
> 1.8.0_261.
>
> [09/01/20 09:26:42] [SSH] Starting sftp client.
>
> [09/01/20 09:26:42] [SSH] Copying latest remoting.jar...
>
> Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent 
> hash is E5FEC468D6F172BF394E1F2571EA686C
>
> Verified agent jar. No update is necessary.
>
> Expanded the channel window size to 4MB
>
> [09/01/20 09:26:55] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
> C:\Java\jdk1.8.0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
> -jar-cache c:\JenkinsSlave/remoting/jarCache
>
> Sep 01, 2020 9:26:56 AM org.jenkinsci.remoting.engine.WorkDirManager 
> initializeWorkDir
>
> INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
>
> Sep 01, 2020 9:26:57 AM org.jenkinsci.remoting.engine.WorkDirManager 
> setupLogging
>
> INFO: Both error and output logs will be printed to 
> c:\JenkinsSlave\remoting
>
> <===[JENKINS REMOTING CAPACITY]===>channel started
>
> Remoting version: 4.3
>
> This is a Windows agent
>
> Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SlaveListener call
>
> INFO: Slave-status listener starting
>
> Sep 01, 2020 9:27:00 AM 
> com.youdevise.hudson.slavestatus.SocketHTTPListener waitForConnection
>
> INFO: Slave-status listener ready on port 3141
>
> [StartupTrigger] - Scanning jobs for node WindowsJG
>
> Agent successfully connected and online
>
>  
>
>  
>
> The one that doesn’t work (Windows 10 64 bits also, using the same Java 
> jdk version):
>
> [09/01/20 14:00:16] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java
>
> [09/01/20 14:00:16] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
> 1.8.0_261.
>
> [09/01/20 14:00:16] [SSH] Starting sftp client.
>
> [09/01/20 14:00:16] [SSH] Copying latest remoting.jar...
>
> [09/01/20 14:00:19] [SSH] Copied 1,522,833 bytes.
>
> Expanded the channel window size to 4MB
>
> [09/01/20 14:00:19] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
> C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
> -jar-cache c:\JenkinsSlave/remoting/jarCache
>
> <===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 2:00:19 PM 
> org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
>
> INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
>
> Sep 01, 2020 2:00:19 PM org.jenkinsci.remoting.engine.WorkDirManager 
> setupLogging
>
> INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
>
> <===[JENKINS REMOTING CAPACITY]===>ERROR: Connection terminated
>
> ERROR:

one downstream with multiple upstreams(all upstreams should be success)

2020-09-01 Thread chenna keshav

Hi,

i have stuck with a small issue... i have a job A which triggers job B and 
job C. for job B and job C downstream job is job D i need this job D is 
to be triggered when job B and job C both are success. i have tried with 
"Build after other projects are build" with "trigger only if build is 
stable" option. its not working for me... the job is getting triggered even 
one of jobs is success. can some one please help me on this..

Thanks,
Keshav.

-- 
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/d9d0f7f6-240e-4559-8e4e-8895e00d0ef2n%40googlegroups.com.

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Jérôme Godbout
Sent: September 1, 2020 2:12 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: Windows client ssh connection error

Did try without the firewall and it doesn’t work either, !?!? Anyone got an 
idea what it is actually doing that might not work?!? Both machine are on the 
same network, no ip conflict. If I delete the remoting.jar and the folders into 
c:\JenkinsSlave it get created again, so the connection is happening and it can 
transfer the file.

From: jenkinsci-users@googlegroups.com 
mailto:jenkinsci-users@googlegroups.com>> On 
Behalf Of Jérôme Godbout
Sent: September 1, 2020 2:05 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: Windows client ssh connection error

Hi,

Is there any special requirements? (ssh does work from both Linux and Windows 
to this machine, also from the Jenkins master user account too). Seem like 
starting the slave fails, anything to do with firewall or something like that?

here the node that work (Windows 10 64 bits):
[09/01/20 09:26:41] [SSH] Checking java version of 
C:\Java\jdk1.8.0_261\/bin/java
[09/01/20 09:26:42] [SSH] C:\Java\jdk1.8.0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 09:26:42] [SSH] Starting sftp client.
[09/01/20 09:26:42] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 09:26:55] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\jdk1.8.0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
Sep 01, 2020 9:26:56 AM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 9:26:57 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 4.3
This is a Windows agent
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SlaveListener call
INFO: Slave-status listener starting
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SocketHTTPListener 
waitForConnection
INFO: Slave-status listener ready on port 3141
[StartupTrigger] - Scanning jobs for node WindowsJG
Agent successfully connected and online


The one that doesn’t work (Windows 10 64 bits also, using the same Java jdk 
version):

[09/01/20 14:00:16] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java

[09/01/20 14:00:16] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.

[09/01/20 14:00:16] [SSH] Starting sftp client.

[09/01/20 14:00:16] [SSH] Copying latest remoting.jar...

[09/01/20 14:00:19] [SSH] Copied 1,522,833 bytes.

Expanded the channel window size to 4MB

[09/01/20 14:00:19] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache

<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 2:00:19 PM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

INFO: Using c:\JenkinsSlave\remoting as a remoting work directory

Sep 01, 2020 2:00:19 PM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging

INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting

<===[JENKINS REMOTING CAPACITY]===>ERROR: Connection terminated

ERROR: java.io.IOException: Unexpected termination of the channel

java.io.EOFException

at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)

at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)

at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)

at java.io.ObjectInputStream.(ObjectInputStream.java:358)

at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)

at hudson.remoting.Command.readFrom(Command.java:142)

at hudson.remoting.Command.readFrom(Command.java:128)

at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)

Caused: java.io.IOException: Unexpected termination of the channel

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel

at hudson.remoting.Request.abort(Request.java:340)

at

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Did try without the firewall and it doesn’t work either, !?!? Anyone got an 
idea what it is actually doing that might not work?!? Both machine are on the 
same network, no ip conflict. If I delete the remoting.jar and the folders into 
c:\JenkinsSlave it get created again, so the connection is happening and it can 
transfer the file.

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Jérôme Godbout
Sent: September 1, 2020 2:05 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: Windows client ssh connection error

Hi,

Is there any special requirements? (ssh does work from both Linux and Windows 
to this machine, also from the Jenkins master user account too). Seem like 
starting the slave fails, anything to do with firewall or something like that?

here the node that work (Windows 10 64 bits):
[09/01/20 09:26:41] [SSH] Checking java version of 
C:\Java\jdk1.8.0_261\/bin/java
[09/01/20 09:26:42] [SSH] C:\Java\jdk1.8.0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 09:26:42] [SSH] Starting sftp client.
[09/01/20 09:26:42] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 09:26:55] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\jdk1.8.0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
Sep 01, 2020 9:26:56 AM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 9:26:57 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 4.3
This is a Windows agent
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SlaveListener call
INFO: Slave-status listener starting
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SocketHTTPListener 
waitForConnection
INFO: Slave-status listener ready on port 3141
[StartupTrigger] - Scanning jobs for node WindowsJG
Agent successfully connected and online


The one that doesn’t work (Windows 10 64 bits also, using the same Java jdk 
version):

[09/01/20 14:00:16] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java

[09/01/20 14:00:16] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.

[09/01/20 14:00:16] [SSH] Starting sftp client.

[09/01/20 14:00:16] [SSH] Copying latest remoting.jar...

[09/01/20 14:00:19] [SSH] Copied 1,522,833 bytes.

Expanded the channel window size to 4MB

[09/01/20 14:00:19] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache

<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 2:00:19 PM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

INFO: Using c:\JenkinsSlave\remoting as a remoting work directory

Sep 01, 2020 2:00:19 PM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging

INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting

<===[JENKINS REMOTING CAPACITY]===>ERROR: Connection terminated

ERROR: java.io.IOException: Unexpected termination of the channel

java.io.EOFException

at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)

at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)

at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)

at java.io.ObjectInputStream.(ObjectInputStream.java:358)

at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)

at hudson.remoting.Command.readFrom(Command.java:142)

at hudson.remoting.Command.readFrom(Command.java:128)

at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)

Caused: java.io.IOException: Unexpected termination of the channel

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel

at hudson.remoting.Request.abort(Request.java:340)

at hudson.remoting.Channel.terminate(Channel.java:1081)

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)

Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
KeilDellGris

   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)

   at hudson.remoting.Request.call(Request.java:202)

   at

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Hi,

Is there any special requirements? (ssh does work from both Linux and Windows 
to this machine, also from the Jenkins master user account too). Seem like 
starting the slave fails, anything to do with firewall or something like that?

here the node that work (Windows 10 64 bits):
[09/01/20 09:26:41] [SSH] Checking java version of 
C:\Java\jdk1.8.0_261\/bin/java
[09/01/20 09:26:42] [SSH] C:\Java\jdk1.8.0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 09:26:42] [SSH] Starting sftp client.
[09/01/20 09:26:42] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 09:26:55] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\jdk1.8.0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
Sep 01, 2020 9:26:56 AM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 9:26:57 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 4.3
This is a Windows agent
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SlaveListener call
INFO: Slave-status listener starting
Sep 01, 2020 9:27:00 AM com.youdevise.hudson.slavestatus.SocketHTTPListener 
waitForConnection
INFO: Slave-status listener ready on port 3141
[StartupTrigger] - Scanning jobs for node WindowsJG
Agent successfully connected and online


The one that doesn’t work (Windows 10 64 bits also, using the same Java jdk 
version):

[09/01/20 14:00:16] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java

[09/01/20 14:00:16] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.

[09/01/20 14:00:16] [SSH] Starting sftp client.

[09/01/20 14:00:16] [SSH] Copying latest remoting.jar...

[09/01/20 14:00:19] [SSH] Copied 1,522,833 bytes.

Expanded the channel window size to 4MB

[09/01/20 14:00:19] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache

<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 2:00:19 PM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

INFO: Using c:\JenkinsSlave\remoting as a remoting work directory

Sep 01, 2020 2:00:19 PM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging

INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting

<===[JENKINS REMOTING CAPACITY]===>ERROR: Connection terminated

ERROR: java.io.IOException: Unexpected termination of the channel

java.io.EOFException

at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)

at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)

at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)

at java.io.ObjectInputStream.(ObjectInputStream.java:358)

at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)

at hudson.remoting.Command.readFrom(Command.java:142)

at hudson.remoting.Command.readFrom(Command.java:128)

at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)

Caused: java.io.IOException: Unexpected termination of the channel

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel

at hudson.remoting.Request.abort(Request.java:340)

at hudson.remoting.Channel.terminate(Channel.java:1081)

at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)

Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
KeilDellGris

   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)

   at hudson.remoting.Request.call(Request.java:202)

   at hudson.remoting.Channel.call(Channel.java:997)

   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)

   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)

   at 
hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:623)

   at 
hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:112)

   at 
hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:457)

   at

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Yes, I created the folder and give the user (I made a local user for this 
called Jenkins). The user has full control over that folder. Does it require 
the user to be admin?
The following are created:
c:\JenkinsSlave\
remoting.jar
remoting\
jarCache\
(empty)
logs\
remoting.log.0
…
remoting.log.4 (all 0 kb file 
empty)

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Ivan Fernandez Calvo
Sent: September 1, 2020 12:05 PM
To: Jenkins Users 
Subject: Re: Windows client ssh connection error

Has the user that connect permissions on c:\JenkinsSlave? Is the folder 
c:\JenkinsSlave\remoting created? Are there some err_pid* files or log files in 
c:\JenkinsSlave folder?
El martes, 1 de septiembre de 2020 a las 17:48:39 UTC+2, Jérôme Godbout 
escribió:
Hi,

I did solve my issue with the ssh agent I had earlier, but when I try to do the 
same on another Windows client machine I get this weird error below. The log on 
the slave are empty (c:\JenkinsSlave\remoting). The error is a bit vague and I 
have no clue what is wrong. I can connect with ssh, I also did it on the master 
node to approve the address to ensure it was not an issue. Seem like the 
exchange stream are breaking down!?! what is going on?

[09/01/20 11:33:18] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java
[09/01/20 11:33:19] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 11:33:19] [SSH] Starting sftp client.
[09/01/20 11:33:19] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 11:33:35] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 11:33:35 AM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 11:33:35 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" 
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360)
at hudson.remoting.Launcher.main(Launcher.java:770)
at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:718)
at hudson.remoting.Launcher.run(Launcher.java:398)
at hudson.remoting.Launcher.main(Launcher.java:298)
ERROR: ERROR: Connection terminated
java.io.IOException: Unexpected termination of the channel
java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.(ObjectInputStream.java:358)
at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:142)
at hudson.remoting.Command.readFrom(Command.java:128)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel
at hudson.remoting.Request.abort(Request.java:340)
at hudson.remoting.Channel.terminate(Channel.java:1081)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
KeilDellGris
   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
   at hudson.remoting.Request.call(Request.java:202)
   at hudson.remoting.Channel.call(Channel.java:997)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)
   at

RE: Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

No nothing

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Ivan Fernandez Calvo
Sent: September 1, 2020 12:20 PM
To: Jenkins Users 
Subject: Re: Windows client ssh connection error

when you enter on that Windows machine though SSH manually, Do you have a long 
banner at the beginning that you do not have in the other machine?
El martes, 1 de septiembre de 2020 a las 18:04:53 UTC+2, Ivan Fernandez Calvo 
escribió:
Has the user that connect permissions on c:\JenkinsSlave? Is the folder 
c:\JenkinsSlave\remoting created? Are there some err_pid* files or log files in 
c:\JenkinsSlave folder?
El martes, 1 de septiembre de 2020 a las 17:48:39 UTC+2, Jérôme Godbout 
escribió:
Hi,

I did solve my issue with the ssh agent I had earlier, but when I try to do the 
same on another Windows client machine I get this weird error below. The log on 
the slave are empty (c:\JenkinsSlave\remoting). The error is a bit vague and I 
have no clue what is wrong. I can connect with ssh, I also did it on the master 
node to approve the address to ensure it was not an issue. Seem like the 
exchange stream are breaking down!?! what is going on?

[09/01/20 11:33:18] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java
[09/01/20 11:33:19] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 11:33:19] [SSH] Starting sftp client.
[09/01/20 11:33:19] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 11:33:35] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 11:33:35 AM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 11:33:35 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" 
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360)
at hudson.remoting.Launcher.main(Launcher.java:770)
at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:718)
at hudson.remoting.Launcher.run(Launcher.java:398)
at hudson.remoting.Launcher.main(Launcher.java:298)
ERROR: ERROR: Connection terminated
java.io.IOException: Unexpected termination of the channel
java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.(ObjectInputStream.java:358)
at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:142)
at hudson.remoting.Command.readFrom(Command.java:128)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel
at hudson.remoting.Request.abort(Request.java:340)
at hudson.remoting.Channel.terminate(Channel.java:1081)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
KeilDellGris
   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
   at hudson.remoting.Request.call(Request.java:202)
   at hudson.remoting.Channel.call(Channel.java:997)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)
   at 
hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:623)
   at 
hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:112)
   at 
hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:457)
   at 
hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   at

Re: pipeline-maven 3.9.0-beta-1

2020-09-01 Thread Arnaud Héritier

We also updated the FAQ:
https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/FAQ.adoc
It is linked from the bottom of the README (AFAIK for now the plugins site
cannot handle the usage of inclusions)

On Tue, Sep 1, 2020 at 5:11 PM Arnaud Héritier  wrote:

> Thanks to we now have converted the documentation from Confluence to
> Asciidoc :
> https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/README.adoc
> I hope the rendering won't be too bad on the plugins site
> All feedbacks (and PRs) are welcome
>
> On Mon, Aug 31, 2020 at 7:54 PM Arnaud Héritier 
> wrote:
>
>> Hi community,
>>
>> We are looking for testers to validate this new release. The version
>> 3.9.0-beta-1 is now available in the Experimental Update Center
>> 
>>  or
>> can be downloaded from:
>> https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.9.0-beta-1/pipeline-maven-3.9.0-beta-1.hpi
>>
>> This is the first release since the handover of the project to @aheritier
>> . Thanks again @cyrille-leclerc
>>  @alvarolobato
>>  for your hard work on it.
>>
>> This release now requires Jenkins core 2.204.6 and refreshed a lot of
>> dependencies (and a bit the codebase).
>> It also brings several new features and fixes.
>>
>> Thanks a lot to all contributors: @bguerin ,
>> @brenuart , @jglick
>> , @JLLeitschuh
>>  .
>>
>> Later this week we'll publish a beta-2 with at the minimum the migration
>> of the documentation from Confluence to the plugin repo (
>> https://github.com/jenkinsci/pipeline-maven-plugin/pull/251 thanks to
>> bthompson0  )
>>
>> Thanks a lot for your help.
>>  New features and improvements
>>
>>- Add support for maven-karma-plugin (#230
>>)
>>@bguerin  - ref: JENKINS-61092
>>
>>
>>  Bug Fixes
>>
>>- Downstream pipelines are not triggered when the artifact has type
>>docker-info (#226
>>)
>>@bguerin  - ref JENKINS-59500
>>
>>- Failed to read XML file produced by maven spy after an execution
>>threw an exception and color is enabled (#232
>>)
>>@brenuart  - ref: JENKINS-61791
>>
>>- Fix groupId used to detect executions of the Tycho Surefire Plugin (
>>#231 )
>>@brenuart  - ref: JENKINS-61790
>>
>>
>>  Internals
>>
>>- Jenkins core upgrade (2.138.4 -> 2.204.6) + Plugin parent upgrade
>>(3.43 -> 4.6) + BOM (#250
>>)
>>@aheritier 
>>- Check either Acegi or Spring Security version of
>>AccessDeniedException, or AccessDeniedException2 or 
>> AccessDeniedException3 (
>>#252 )
>>@jglick 
>>- Use official version of GeneralNonBlockingStepExecution (#199
>>) @jglick
>> - ref JENKINS-49337
>>
>>- Code refresh (#276
>>)
>>@aheritier 
>>- Upgrade Jenkins incremental to latest (1.1) (#249
>>)
>>@aheritier 
>>- Update maven-wrapper to the latest and mvn to 3.6.3 (#248
>>)
>>@aheritier 
>>- Use HTTPS to resolve dependencies in Maven Build (Tests projects) (
>>#229 )
>>@JLLeitschuh 
>>
>>  Dependency updates
>>
>>- Bump htmlpublisher from 1.16 to 1.23 (#265
>>)
>>@dependabot 
>>- Bump docker-fixtures from 1.8 to 1.10 (#274
>>)
>>@dependabot 
>>

Re: Windows client ssh connection error

2020-09-01 Thread Ivan Fernandez Calvo

when you enter on that Windows machine though SSH manually, Do you have a 
long banner at the beginning that you do not have in the other machine?

El martes, 1 de septiembre de 2020 a las 18:04:53 UTC+2, Ivan Fernandez 
Calvo escribió:

> Has the user that connect permissions on c:\JenkinsSlave? Is the folder 
> c:\JenkinsSlave\remoting created? Are there some err_pid* files or log 
> files in c:\JenkinsSlave folder?
>
> El martes, 1 de septiembre de 2020 a las 17:48:39 UTC+2, Jérôme Godbout 
> escribió:
>
>> Hi,
>>
>>  
>>
>> I did solve my issue with the ssh agent I had earlier, but when I try to 
>> do the same on another Windows client machine I get this weird error below. 
>> The log on the slave are empty (c:\JenkinsSlave\remoting). The error is 
>> a bit vague and I have no clue what is wrong. I can connect with ssh, I 
>> also did it on the master node to approve the address to ensure it was not 
>> an issue. Seem like the exchange stream are breaking down!?! what is going 
>> on?
>>
>>  
>>
>> [09/01/20 11:33:18] [SSH] Checking java version of 
>> C:\Java\1_8_0_261\/bin/java
>>
>> [09/01/20 11:33:19] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
>> 1.8.0_261.
>>
>> [09/01/20 11:33:19] [SSH] Starting sftp client.
>>
>> [09/01/20 11:33:19] [SSH] Copying latest remoting.jar...
>>
>> Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent 
>> hash is E5FEC468D6F172BF394E1F2571EA686C
>>
>> Verified agent jar. No update is necessary.
>>
>> Expanded the channel window size to 4MB
>>
>> [09/01/20 11:33:35] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
>> C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
>> -jar-cache c:\JenkinsSlave/remoting/jarCache
>>
>> <===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 11:33:35 AM 
>> org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
>>
>> INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
>>
>> Sep 01, 2020 11:33:35 AM org.jenkinsci.remoting.engine.WorkDirManager 
>> setupLogging
>>
>> INFO: Both error and output logs will be printed to 
>> c:\JenkinsSlave\remoting
>>
>> <===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" 
>> java.io.EOFException: unexpected stream termination
>>
>> at 
>> hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415)
>>
>> at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360)
>>
>> at hudson.remoting.Launcher.main(Launcher.java:770)
>>
>> at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:718)
>>
>> at hudson.remoting.Launcher.run(Launcher.java:398)
>>
>> at hudson.remoting.Launcher.main(Launcher.java:298)
>>
>> ERROR: ERROR: Connection terminated
>>
>> java.io.IOException: Unexpected termination of the channel
>>
>> java.io.EOFException
>>
>> at 
>> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
>>
>> at 
>> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
>>
>> at 
>> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
>>
>> at java.io.ObjectInputStream.(ObjectInputStream.java:358)
>>
>> at 
>> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
>>
>> at hudson.remoting.Command.readFrom(Command.java:142)
>>
>> at hudson.remoting.Command.readFrom(Command.java:128)
>>
>> at 
>> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
>>
>> at 
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
>>
>> Caused: java.io.IOException: Unexpected termination of the channel
>>
>> at 
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
>>
>> hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
>> termination of the channel
>>
>> at hudson.remoting.Request.abort(Request.java:340)
>>
>> at hudson.remoting.Channel.terminate(Channel.java:1081)
>>
>> at 
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)
>>
>> Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote 
>> call to KeilDellGris
>>
>>at 
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
>>
>>at hudson.remoting.Request.call(Request.java:202)
>>
>>at hudson.remoting.Channel.call(Channel.java:997)
>>
>>at 
>> hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
>>
>>at 
>> hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)
>>
>>at 
>> hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:623)
>>
>>at 
>> hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:112)
>>
>>at 
>>

Re: Windows client ssh connection error

2020-09-01 Thread Ivan Fernandez Calvo

Has the user that connect permissions on c:\JenkinsSlave? Is the folder 
c:\JenkinsSlave\remoting created? Are there some err_pid* files or log 
files in c:\JenkinsSlave folder?

El martes, 1 de septiembre de 2020 a las 17:48:39 UTC+2, Jérôme Godbout 
escribió:

> Hi,
>
>  
>
> I did solve my issue with the ssh agent I had earlier, but when I try to 
> do the same on another Windows client machine I get this weird error below. 
> The log on the slave are empty (c:\JenkinsSlave\remoting). The error is a 
> bit vague and I have no clue what is wrong. I can connect with ssh, I also 
> did it on the master node to approve the address to ensure it was not an 
> issue. Seem like the exchange stream are breaking down!?! what is going on?
>
>  
>
> [09/01/20 11:33:18] [SSH] Checking java version of 
> C:\Java\1_8_0_261\/bin/java
>
> [09/01/20 11:33:19] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
> 1.8.0_261.
>
> [09/01/20 11:33:19] [SSH] Starting sftp client.
>
> [09/01/20 11:33:19] [SSH] Copying latest remoting.jar...
>
> Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent 
> hash is E5FEC468D6F172BF394E1F2571EA686C
>
> Verified agent jar. No update is necessary.
>
> Expanded the channel window size to 4MB
>
> [09/01/20 11:33:35] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
> C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
> -jar-cache c:\JenkinsSlave/remoting/jarCache
>
> <===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 11:33:35 AM 
> org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
>
> INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
>
> Sep 01, 2020 11:33:35 AM org.jenkinsci.remoting.engine.WorkDirManager 
> setupLogging
>
> INFO: Both error and output logs will be printed to 
> c:\JenkinsSlave\remoting
>
> <===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" 
> java.io.EOFException: unexpected stream termination
>
> at 
> hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415)
>
> at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360)
>
> at hudson.remoting.Launcher.main(Launcher.java:770)
>
> at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:718)
>
> at hudson.remoting.Launcher.run(Launcher.java:398)
>
> at hudson.remoting.Launcher.main(Launcher.java:298)
>
> ERROR: ERROR: Connection terminated
>
> java.io.IOException: Unexpected termination of the channel
>
> java.io.EOFException
>
> at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
>
> at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
>
> at 
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
>
> at java.io.ObjectInputStream.(ObjectInputStream.java:358)
>
> at 
> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
>
> at hudson.remoting.Command.readFrom(Command.java:142)
>
> at hudson.remoting.Command.readFrom(Command.java:128)
>
> at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
>
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
>
> Caused: java.io.IOException: Unexpected termination of the channel
>
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
>
> hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
> termination of the channel
>
> at hudson.remoting.Request.abort(Request.java:340)
>
> at hudson.remoting.Channel.terminate(Channel.java:1081)
>
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)
>
> Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote 
> call to KeilDellGris
>
>at 
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
>
>at hudson.remoting.Request.call(Request.java:202)
>
>at hudson.remoting.Channel.call(Channel.java:997)
>
>at 
> hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
>
>at 
> hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)
>
>at 
> hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:623)
>
>at 
> hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:112)
>
>at 
> hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:457)
>
>at 
> hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
>
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
>at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
>at 
>

Windows client ssh connection error

2020-09-01 Thread Jérôme Godbout

Hi,

I did solve my issue with the ssh agent I had earlier, but when I try to do the 
same on another Windows client machine I get this weird error below. The log on 
the slave are empty (c:\JenkinsSlave\remoting). The error is a bit vague and I 
have no clue what is wrong. I can connect with ssh, I also did it on the master 
node to approve the address to ensure it was not an issue. Seem like the 
exchange stream are breaking down!?! what is going on?

[09/01/20 11:33:18] [SSH] Checking java version of C:\Java\1_8_0_261\/bin/java
[09/01/20 11:33:19] [SSH] C:\Java\1_8_0_261\/bin/java -version returned 
1.8.0_261.
[09/01/20 11:33:19] [SSH] Starting sftp client.
[09/01/20 11:33:19] [SSH] Copying latest remoting.jar...
Source agent hash is E5FEC468D6F172BF394E1F2571EA686C. Installed agent hash is 
E5FEC468D6F172BF394E1F2571EA686C
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[09/01/20 11:33:35] [SSH] Starting agent process: cd "c:\JenkinsSlave" && 
C:\Java\1_8_0_261\/bin/java  -jar remoting.jar -workDir c:\JenkinsSlave 
-jar-cache c:\JenkinsSlave/remoting/jarCache
<===[JENKINS REMOTING CAPACITY]===>Sep 01, 2020 11:33:35 AM 
org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\JenkinsSlave\remoting as a remoting work directory
Sep 01, 2020 11:33:35 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to c:\JenkinsSlave\remoting
<===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" 
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:415)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:360)
at hudson.remoting.Launcher.main(Launcher.java:770)
at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:718)
at hudson.remoting.Launcher.run(Launcher.java:398)
at hudson.remoting.Launcher.main(Launcher.java:298)
ERROR: ERROR: Connection terminated
java.io.IOException: Unexpected termination of the channel
java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.(ObjectInputStream.java:358)
at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:142)
at hudson.remoting.Command.readFrom(Command.java:128)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
termination of the channel
at hudson.remoting.Request.abort(Request.java:340)
at hudson.remoting.Channel.terminate(Channel.java:1081)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:94)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
KeilDellGris
   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
   at hudson.remoting.Request.call(Request.java:202)
   at hudson.remoting.Channel.call(Channel.java:997)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
   at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:424)
   at 
hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:623)
   at 
hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:112)
   at 
hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:457)
   at 
hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
Caused by: java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at

Re: pipeline-maven 3.9.0-beta-1

2020-09-01 Thread Arnaud Héritier

Thanks to we now have converted the documentation from Confluence to
Asciidoc :
https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/README.adoc
I hope the rendering won't be too bad on the plugins site
All feedbacks (and PRs) are welcome

On Mon, Aug 31, 2020 at 7:54 PM Arnaud Héritier  wrote:

> Hi community,
>
> We are looking for testers to validate this new release. The version
> 3.9.0-beta-1 is now available in the Experimental Update Center
> 
>  or
> can be downloaded from:
> https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.9.0-beta-1/pipeline-maven-3.9.0-beta-1.hpi
>
> This is the first release since the handover of the project to @aheritier
> . Thanks again @cyrille-leclerc
>  @alvarolobato
>  for your hard work on it.
>
> This release now requires Jenkins core 2.204.6 and refreshed a lot of
> dependencies (and a bit the codebase).
> It also brings several new features and fixes.
>
> Thanks a lot to all contributors: @bguerin ,
> @brenuart , @jglick
> , @JLLeitschuh 
>  .
>
> Later this week we'll publish a beta-2 with at the minimum the migration
> of the documentation from Confluence to the plugin repo (
> https://github.com/jenkinsci/pipeline-maven-plugin/pull/251 thanks to
> bthompson0  )
>
> Thanks a lot for your help.
>  New features and improvements
>
>- Add support for maven-karma-plugin (#230
>) @bguerin
> - ref: JENKINS-61092
>
>
>  Bug Fixes
>
>- Downstream pipelines are not triggered when the artifact has type
>docker-info (#226
>) @bguerin
> - ref JENKINS-59500
>
>- Failed to read XML file produced by maven spy after an execution
>threw an exception and color is enabled (#232
>)
>@brenuart  - ref: JENKINS-61791
>
>- Fix groupId used to detect executions of the Tycho Surefire Plugin (
>#231 )
>@brenuart  - ref: JENKINS-61790
>
>
>  Internals
>
>- Jenkins core upgrade (2.138.4 -> 2.204.6) + Plugin parent upgrade
>(3.43 -> 4.6) + BOM (#250
>)
>@aheritier 
>- Check either Acegi or Spring Security version of
>AccessDeniedException, or AccessDeniedException2 or AccessDeniedException3 
> (
>#252 )
>@jglick 
>- Use official version of GeneralNonBlockingStepExecution (#199
>) @jglick
> - ref JENKINS-49337
>
>- Code refresh (#276
>)
>@aheritier 
>- Upgrade Jenkins incremental to latest (1.1) (#249
>)
>@aheritier 
>- Update maven-wrapper to the latest and mvn to 3.6.3 (#248
>)
>@aheritier 
>- Use HTTPS to resolve dependencies in Maven Build (Tests projects) (
>#229 )
>@JLLeitschuh 
>
>  Dependency updates
>
>- Bump htmlpublisher from 1.16 to 1.23 (#265
>)
>@dependabot 
>- Bump docker-fixtures from 1.8 to 1.10 (#274
>)
>@dependabot 
>- Bump groovy-all from 2.4.12 to 2.4.20 (#273
>)
>@dependabot 
>- Bump slf4j-api from 1.7.26 to 1.7.30 (#267
>)
>@dependabot 
>- Bump maven-shared-utils from

The placement of the `checkout' step in `matrix' pipeline jobs

2020-09-01 Thread Anton Shepelev

Hello, all

How is `matrix' supposed to interact with `checkout'?  If I
have several axes, of which some require change of agent (OS
version), and some do not (Debug or Release mode), where
shall place the `checkout' step?  Currently, I have it at
this path in my Jenkinsfile:

   pipeline -> stages -> stage('All')  ->
   matrix   -> stages -> stage('Build') -> steps

-- that is, inside a matrix cell.  Therefore, a checkout is
executed for each cell, regardless of whether it had already
been done on the same agent machine. Is it intended usage of
the `matrix' element?  If not, how can I cause checkout to
be performed once per agent, rather than once per matrix
cell?

-- 
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/20200901172344.87f1525cb0a6b5630e4941c1%40gmail.com.

Re: How to start, in a Jenkinsfile, a multibranch job inside a Bitbucket folder?

2020-09-01 Thread Amedee Van Gasse

The problem was with the folder name `iText%207%20.NET`, which is an 
urlencoded version of `iText 7 .NET`. Apparently Jenkins can't handle 
urlencoded spaces in folder names.

I renamed the folder to `itext_7_dotnet` and then used

build job: "itext_7_dotnet/sharpen/${java.net.URLEncoder.encode 
branchName, 'UTF-8'}"

This works.


Moral of the story: never use spaces in your folder names!

On Tuesday, September 1, 2020 at 8:28:42 AM UTC+2 Amedee Van Gasse wrote:

> In a Jenkinsfile, to start a parameterized pipeline job from another job, 
> I have this code snippet:
>
> build job: 'build-sharpen-branch', parameters: [
> [$class: 'StringParameterValue', name: 'BRANCHNAME', value: 
> mergeBranchname]
> ]
>
> This already works as expected, and it will start a job at URL 
> `https://$JENKINS_URL/job/build-sharpen-branch/`.
>
> Now I want to start a job, that is one branch of a multibranch project 
> inside a Bitbucket folder. The URL of the job is 
> `https://$JENKINS_URL/job/iText%207%
> 20.NET/job/sharpen/job/feature%2FQA-10738/` 
> .
> * `iText%207%20.NET` is the name of the Bitbucket project.
> * `sharpen` is the name of the Multibranch job.
> * `feature%2FQA-10738` is the name of the branch, urlencoded.
>
> I read the following Stack Overflow questions about starting a multibranch 
> job NOT inside a folder:
> * 
> https://stackoverflow.com/questions/50909730/trigger-multibranch-job-from-another
> * 
> https://stackoverflow.com/questions/45010601/triggering-a-multibranch-pipeline-job-from-an-other-multibranch-pipeline
> * 
> https://stackoverflow.com/questions/37322143/how-to-trigger-multibranch-pipeline-jenkins-job-within-regular-pipeline-job
>
> From the answers there, I gather that the syntax is `$JOB/$BRANCH` (where 
> `$BRANCH` is URL-encoded to rename branches like `feature/foo` to 
> `feature%2Ffoo`).
>
> From 
> https://stackoverflow.com/questions/41182186/jenkins-pipeline-with-folder-plugin-how-to-build-a-job-located-different-folder
>  
> I gather that the syntax for a job inside a folder is `$FOLDER/$JOB`.
>
> Combining the two, I conclude that the syntax for folder+job+branch is 
> most likely `$FOLDER/$JOB/$BRANCH`.
>
> So I tried with this code:
>
> build job: "iText%207%20.NET/sharpen/${java.net.URLEncoder.encode 
>  branchName, 
> 'UTF-8'}"
>
> with
>
> * folder = `iText%207%20.NET`
> * job = `sharpen`
> * branch = `${java.net.URLEncoder.encode branchName, 'UTF-8'}` 
> *(URLEncoder to change `/` in the branch name to `%2F`)*
>
> To my surprise, when I ran this, I got an error:
>
> > ERROR: No item named iText%207%20.NET/sharpen/feature%2FQA-10738 found
>
> As already stated above, a job exists on URL 
> `https://$JENKINS_URL/job/iText%207%
> 20.NET/job/sharpen/job/feature%2FQA-10738/` 
> .
>
> What is the correct syntax for a multibranch job inside a Bitbucket folder?
>

-- 
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/aedeb36d-caa9-4368-8638-6a528fce551fn%40googlegroups.com.

How to start, in a Jenkinsfile, a multibranch job inside a Bitbucket folder?

2020-09-01 Thread Amedee Van Gasse

In a Jenkinsfile, to start a parameterized pipeline job from another job, I 
have this code snippet:

build job: 'build-sharpen-branch', parameters: [
[$class: 'StringParameterValue', name: 'BRANCHNAME', value: 
mergeBranchname]
]

This already works as expected, and it will start a job at URL 
`https://$JENKINS_URL/job/build-sharpen-branch/`.

Now I want to start a job, that is one branch of a multibranch project 
inside a Bitbucket folder. The URL of the job is 
`https://$JENKINS_URL/job/iText%207%20.NET/job/sharpen/job/feature%2FQA-10738/`.
* `iText%207%20.NET` is the name of the Bitbucket project.
* `sharpen` is the name of the Multibranch job.
* `feature%2FQA-10738` is the name of the branch, urlencoded.

I read the following Stack Overflow questions about starting a multibranch 
job NOT inside a folder:
* 
https://stackoverflow.com/questions/50909730/trigger-multibranch-job-from-another
* 
https://stackoverflow.com/questions/45010601/triggering-a-multibranch-pipeline-job-from-an-other-multibranch-pipeline
* 
https://stackoverflow.com/questions/37322143/how-to-trigger-multibranch-pipeline-jenkins-job-within-regular-pipeline-job

>From the answers there, I gather that the syntax is `$JOB/$BRANCH` (where 
`$BRANCH` is URL-encoded to rename branches like `feature/foo` to 
`feature%2Ffoo`).

>From 
https://stackoverflow.com/questions/41182186/jenkins-pipeline-with-folder-plugin-how-to-build-a-job-located-different-folder
 
I gather that the syntax for a job inside a folder is `$FOLDER/$JOB`.

Combining the two, I conclude that the syntax for folder+job+branch is most 
likely `$FOLDER/$JOB/$BRANCH`.

So I tried with this code:

build job: "iText%207%20.NET/sharpen/${java.net.URLEncoder.encode 
branchName, 'UTF-8'}"

with

* folder = `iText%207%20.NET`
* job = `sharpen`
* branch = `${java.net.URLEncoder.encode branchName, 'UTF-8'}` *(URLEncoder 
to change `/` in the branch name to `%2F`)*

To my surprise, when I ran this, I got an error:

> ERROR: No item named iText%207%20.NET/sharpen/feature%2FQA-10738 found

As already stated above, a job exists on URL 
`https://$JENKINS_URL/job/iText%207%20.NET/job/sharpen/job/feature%2FQA-10738/`.

What is the correct syntax for a multibranch job inside a Bitbucket folder?

-- 
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/cd092530-9717-4ca1-927a-04fa92c0284cn%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

Re: Unable to Update Jenkins and Plugin

Re: Unable to Update Jenkins and Plugin

Re: Jenkins Integration with LDAP - Testing Connection Fails

Re: Unable to Update Jenkins and Plugin

Unable to Update Jenkins and Plugin

convert declarative pipeline stage to scripted pipeline

Re: one downstream with multiple upstreams(all upstreams should be success)

RE: Windows client ssh connection error

Re: one downstream with multiple upstreams(all upstreams should be success)

Re: Windows client ssh connection error

one downstream with multiple upstreams(all upstreams should be success)

RE: Windows client ssh connection error

RE: Windows client ssh connection error

RE: Windows client ssh connection error

RE: Windows client ssh connection error

RE: Windows client ssh connection error

Re: pipeline-maven 3.9.0-beta-1

Re: Windows client ssh connection error

Re: Windows client ssh connection error

Windows client ssh connection error

Re: pipeline-maven 3.9.0-beta-1

The placement of the `checkout' step in `matrix' pipeline jobs

Re: How to start, in a Jenkinsfile, a multibranch job inside a Bitbucket folder?

How to start, in a Jenkinsfile, a multibranch job inside a Bitbucket folder?

25 matches

Site Navigation

Mail list logo

Footer information