[JIRA] (JENKINS-39054) Shell interpreter doesn't work on windows when PATH to sh.exe contains a space

2019-04-24 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann commented on  JENKINS-39054  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shell interpreter doesn't work on windows when PATH to sh.exe contains a space   
 

  
 
 
 
 

 
 I am using Git for Windows and Shell scripts exactly as expected above. This is on Windows 7 Pro + Windows 10, Java SE 8, on Jenkins master and agent nodes. It works. sh.exe is located through PATH, no further Jenkins configuration required. Known limitations: 
 
Add "c:\Program Files\Git\bin" to System Path, then reboot. 
Software updates can remove "c:\Program Files\Git\bin" from the search path. 
For pipelines, nohup.exe must be on the path, as in JENKINS-33708. 
    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53189) Exception during Test LDAP settings in group search filter

2018-08-22 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53189  
 
 
  Exception during Test LDAP settings in group search filter   
 

  
 
 
 
 

 
Change By: 
 Peter Vohmann  
 

  
 
 
 
 

 
 As I configure LDAP and press Test LDAP settings,  then fill my user ID and password,  the following exception appears.I understand that "/" must be excaped in LDAP queries as \27.The Group search filter is (&(objectclass=group)(cn=\{0})) . Some other user IDs are not causing exceptions as they are not member in those fancy groups. Our productive use with simple named groups is not affected. Removing the search filter  get rids  also gets rid  of the exception, but then groups cannot be used for authorization at all  anymore .  (active directory)  javax.naming.InvalidNameException: Invalid name: "CN=BU1/XDEP,OU=Departments,OU=Bu00,OU=Distributionlists,OU=Cng4,DC=EU",DC=example,DC=com at javax.naming.ldap.Rfc2253Parser.parseAttrType(Rfc2253Parser.java:155) at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:108) at javax.naming.ldap.Rfc2253Parser.parseDn(Rfc2253Parser.java:70) at javax.naming.ldap.LdapName.parse(LdapName.java:785) at javax.naming.ldap.LdapName.(LdapName.java:123) at hudson.security.LDAPSecurityRealm$GroupDetailsMapper.mapAttributes(LDAPSecurityRealm.java:972) at hudson.security.LDAPSecurityRealm$GroupDetailsMapper.mapAttributes(LDAPSecurityRealm.java:969) at jenkins.security.plugins.ldap.LDAPExtendedTemplate$SearchResultEnumeration.next(LDAPExtendedTemplate.java:163) at jenkins.security.plugins.ldap.LDAPExtendedTemplate.searchForFirstEntry(LDAPExtendedTemplate.java:74)Caused: org.acegisecurity.ldap.LdapDataAccessException: Unable to get first element; nested exception is javax.naming.InvalidNameException: Invalid name: "CN=BU1/XDEP,OU=Departments,OU=Bu00,OU=Distributionlists,OU=Cng4,DC=EU",DC=example,DC=com at jenkins.security.plugins.ldap.LDAPExtendedTemplate.searchForFirstEntry(LDAPExtendedTemplate.java:76) at hudson.security.LDAPSecurityRealm.searchForGroupName(LDAPSecurityRealm.java:895) at hudson.security.LDAPSecurityRealm.loadGroupByGroupname(LDAPSecurityRealm.java:876) at hudson.security.LDAPSecurityRealm.loadGroupByGroupname(LDAPSecurityRealm.java:848) at hudson.security.LDAPSecurityRealm$DescriptorImpl.validate(LDAPSecurityRealm.java:1903) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1595) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734)Ca

[JIRA] (JENKINS-53189) Exception during Test LDAP settings in group search filter

2018-08-22 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53189  
 
 
  Exception during Test LDAP settings in group search filter   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 ldap-plugin  
 
 
Created: 
 2018-08-22 15:36  
 
 
Environment: 
 Jenkins 2.121.3, ldap-plugin 1.20  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Peter Vohmann  
 

  
 
 
 
 

 
 As I configure LDAP and press Test LDAP settings, the following exception appears. I understand that "/" must be excaped in LDAP queries as \27. The Group search filter is (&(objectclass=group)(cn={0})) . Removing the search filter get rids of the exception, but then groups cannot be used for authorization at all anymore.   javax.naming.InvalidNameException: Invalid name: "CN=BU1/XDEP,OU=Departments,OU=Bu00,OU=Distributionlists,OU=Cng4,DC=EU",DC=example,DC=com at javax.naming.ldap.Rfc2253Parser.parseAttrType(Rfc2253Parser.java:155) at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:108) at javax.naming.ldap.Rfc2253Parser.parseDn(Rfc2253Parser.java:70) at javax.naming.ldap.LdapName.parse(LdapName.java:785) at javax.naming.ldap.LdapName.(LdapName.java:123) at hudson.security.LDAPSecurityRealm$GroupDetailsMapper.mapAttributes(LDAPSecurityRealm.java:972) at hudson.security.LDAPSecurityRealm$GroupDetailsMapper.mapAttributes(LDAPSecurityRealm.java:969) at jenkins.security.plugins.ldap.LDAPExtendedTemplate$SearchResultEnumeration.next(LDAPExtendedTemplate.java:163) at jenkins.security.plugins.ldap.LDAPExtendedTemplate.searchForFirstEntry(LDAPExtendedTemplate.java:74) Caused: org.acegisecurity.ldap.LdapDataAccessException: Unable to get first element; nested exception is javax.naming.InvalidNameException: Invalid name: "CN=BU1/XDEP,OU=Departments,OU=Bu00,OU=Distributionlists,OU=Cng4,DC=EU",DC=example,DC=com at jenkins.security.plugins.ldap.LDAPExtendedTemplate.

[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent

2017-03-21 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann edited a comment on  JENKINS-42959  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed known_hosts verification for SSH agent   
 

  
 
 
 
 

 
 I had the same issue, cygwin ssh added the ecdsa-sha2-nistp256 type key to known hosts.One can  get  add  all known types with  *  ssh-keyscan  >>known_hosts  to satisfy * this did include the RSA key for  ssh-slave.Observed with cygwin ssh (OpenSSH_6.8p1, OpenSSL 1.0.2a 19 Mar 2015)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent

2017-03-21 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann commented on  JENKINS-42959  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed known_hosts verification for SSH agent   
 

  
 
 
 
 

 
 I had the same issue, cygwin ssh added the ecdsa-sha2-nistp256 type key to known hosts. One can get all known types with ssh-keyscan  >>known_hosts to satisfy ssh-slave. Observed with cygwin ssh (OpenSSH_6.8p1, OpenSSL 1.0.2a 19 Mar 2015)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

2016-11-28 Thread peter.vohm...@de.bosch.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Vohmann commented on  JENKINS-33185  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Visualize parallel steps within a Pipeline Stage   
 

  
 
 
 
 

 
 We have a use case to drive parallel builds over multiple stages, since we code C++ for multiple architectures and environments. Would this be possible with the Pipeline Stage, or even Pipeline at its core? In the example you see 
 
Multiple design targets of the code lead to parallel streams of execution, 
The same stages occur in every stream. 
 I expect to 
 
Name a Stage not only on top level, but also within a node step. 
Be able to *reuse* the Stage by name -> collect certain activity in the same Stage column. 
visualize multiple steps under the same Stage title. 
Within a Node(eg "B") step, switch stage -> split output from same node to two Stages. 
 The Build and Test Stages would be active at the same time, depending on design stream. Output from this pipeline should be separated into exactly three Stages and activity within each stage. 
 
Setup.Default.console 
Build.web.console 
Build.embedded.console 
Test.web.console 
Test.embedded.test-lowend.console 
Test.embedded.test-highend.console 
 

 

node('A') {
stage('Setup') {
println 'Preparing multiple builds'
}
}
parallel (
"web" : {
node('B') {
stage('Build') {
println 'Build web application'
}
stage('Test') {
println 'Selenium Tests'
}
}
},
"embedded" : {
node('C') {
stage('Build') {
println 'Build embedded solution'
}
}
stage('Test') {
parallel (
"test-lowend" : {
node('D1') {
println 'Test lowend embedded'
}
}, 
"test-highend" : {
node('D2') {
println 'Build highend embedded'
}
}
)
}
}
)