[JIRA] (JENKINS-49250) Missing "trunk" from svn Multibranch Pipeline after Update
Title: Message Title heinzepreller resolved as Fixed Problem is gone after updating to jenkins 2.109 and updating all of the Pipeline Plugins Jenkins / JENKINS-49250 Missing "trunk" from svn Multibranch Pipeline after Update Change By: heinzepreller Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-42880) env variables suddenly gone
Title: Message Title heinzepreller updated an issue Jenkins / JENKINS-42880 env variables suddenly gone Change By: heinzepreller Priority: Minor Major 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-42880) env variables suddenly gone
Title: Message Title heinzepreller created an issue Jenkins / JENKINS-42880 env variables suddenly gone Issue Type: Bug Assignee: Matt Love Components: environment-manager-tools-plugin Created: 2017/Mar/17 1:19 PM Environment: Ubuntu 14.04 Labels: env property Priority: Minor Reporter: heinzepreller Hi, we upgraded from jenkins 2.47 to 2.50 since then nearly all of our ant build steps are failing. I found out why : We have following checks in our ANT Scripts: "env.ANT_HOME" message="SYSTEMCONFIGFAILURE: Variable ANT_HOME must be set!" /> Problem is we are using property "env"/> And "env" is suddenly empty - nothing else changed, ANT_HOME for example is set but check is failing. I didn't find any clue in jenkins changelog or here in JIRA so im filing this isssue.
[JIRA] [workflow-plugin] (JENKINS-34595) Multibranch Pipeline Project vs SVN branches
Title: Message Title heinzepreller resolved as Duplicate Jenkins / JENKINS-34595 Multibranch Pipeline Project vs SVN branches Change By: heinzepreller Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34595) Multibranch Pipeline Project vs SVN branches
Title: Message Title heinzepreller commented on JENKINS-34595 Re: Multibranch Pipeline Project vs SVN branches sorry just saw this is a duplicate of JENKINS-34564 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34595) Multibranch Pipeline Project vs SVN branches
Title: Message Title heinzepreller created an issue Jenkins / JENKINS-34595 Multibranch Pipeline Project vs SVN branches Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/04 9:58 AM Environment: ubuntu lts 14.04, jenkins 2.1 Labels: workflow 2.1 Priority: Major Reporter: heinzepreller Hi, i d'like to use the multibranch Feature with Workflow Plugin Pipelines but it's nearly not possible because of some weird naming for branches. Lets say i have specified some SVN URL svn://URL/Project. Under this URL there are a trunk Folder (svn://URL/Project/trunk) and some branch Folders (svn://URL/Project/branches/1.0, svn://URL/Project/branches/2.0). Jenkins scans the structure and creates 3 Projects: trunk
[JIRA] [active-directory-plugin] (JENKINS-28664) LDAPS Authorization not possible
Title: Message Title heinzepreller commented on JENKINS-28664 Re: LDAPS Authorization not possible Still not able to use ldaps: Jenkins ver. 1.622 Active Directory plugin 1.41 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28664) LDAPS Authorization not possible
Title: Message Title heinzepreller created an issue Jenkins / JENKINS-28664 LDAPS Authorization not possible Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 01/Jun/15 7:33 AM Environment: Ubuntu 14.04.2 LTS Jenkins ver. 1.614 Active Directory plugin 1.39 Java 1.7.0_79-b14 Priority: Major Reporter: heinzepreller Hi, i'm trying to secure LDAP Logon so i decided to switch from LDAP to LDAPS. I tried both LDAPS Ports 3269 and 636 with Test in Global Security Config but none of them are working. I'm getting immediate Error: Bad bind username or password org.acegisecurity.BadCredentialsException: Either no such user 'CN=XX,OU=X,OU=XXX,DC=,DC=XX' or incorrect password; nested exception is javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms. at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:453) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.doValidate(ActiveDirectorySecurityRealm.java:369) at
[JIRA] [active-directory-plugin] (JENKINS-28664) LDAPS Authorization not possible
Title: Message Title
heinzepreller updated an issue
Jenkins / JENKINS-28664
LDAPS Authorization not possible
Change By:
heinzepreller
Hi,i'mtryingtosecureLDAPLogonsoidecidedtoswitchfromLDAPtoLDAPS.ItriedbothLDAPSPorts3269and636withTestinGlobalSecurityConfigbutnoneofthemareworking. !GlobalConfig.png|thumbnail! I'mgettingimmediateError:{code}Badbindusernameorpasswordorg.acegisecurity.BadCredentialsException:Eithernosuchuser'CN=XX,OU=X,OU=XXX,DC=,DC=XX'orincorrectpassword;nestedexceptionisjavax.naming.NamingException:LDAPresponsereadtimedout,timeoutused:-1ms. athudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:453) athudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.doValidate(ActiveDirectorySecurityRealm.java:369) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
[JIRA] [active-directory-plugin] (JENKINS-28664) LDAPS Authorization not possible
Title: Message Title heinzepreller updated an issue Jenkins / JENKINS-28664 LDAPS Authorization not possible Change By: heinzepreller Attachment: GlobalConfig.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-27455) Jenkins fails to start after update - job history is gone
heinzepreller created JENKINS-27455 Jenkins fails to start after update - job history is gone Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Mar/15 8:07 AM Description: Hi there, we had some problems updating jenkins on our Windows 2008 R2 Server from Version 1.593 to 1.599. After starting our tomcat with the new war-file jenkins didn't start - i tried several times. I noticed the following symptoms: 100 % processing load RAM of tomcat was about 1024 MB - normally this is about 2,5 GB after fresh start tomcat job was loading the jenkins war over and over again jenkins tried to migrate jobs but got errors So i copied the old war back to tomcat and jenkins was starting normally. But then i noticed that nearly every build history of all of my 350 jobs was gone. It seems there are Problems with Symbolic Links and "Latest Build" Folders. Is anyone else facing such problems ? How can i fix this ? Is any future update fixing this? Environment: Windows 2008 R2 Project: Jenkins Priority: Critical Reporter: heinzepreller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials We are still not able to build releases with "artifactory release staging" since a week now, because of missing credntials artifactory tag commit. Any ideas, any workarounds ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Upgrade of Subversion Plugin to v 2.2 didn't change anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller edited a comment on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Upgrade of Subversion Plugin to v 2.2 didn't change anything. Also "Release Staging" build to build a Release for Artifactory is not possible anymore, because VCS cannot be tagged and pom.xml cannto be commit because of missing credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Same to me: After Upgrade to Jenkins 1.551 and Subversion Plugin 2.1 we aren't able to VCS Tag after "Release Staging" Build. Also pom commit fails with Subversion Plug-in: "Failure in post build SCM action: svn: E200015: OPTIONS" I don't know where to specify credentials for Artifactory Plugin or something else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
heinzepreller commented on JENKINS-20630 Jenkins fails to start Same problem here, update from 1.538 to 1.540 fails on Windows x64 Server with tomcat as service. Service starts over and over again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17703) Active Directory plugin crashes on version 1.31 (2013/04/18)
heinzepreller commented on JENKINS-17703 Active Directory plugin crashes on version 1.31 (2013/04/18) We are facing a similar issue. The main difference is that only people with german Umlauts (äöü) in their Names aren't allowed to login. After role back to 1.30 everything works fine again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17692) Active Directory Plugin - Fails to retreive users with swedish characters in full name
heinzepreller commented on JENKINS-17692 Active Directory Plugin - Fails to retreive users with swedish characters in full name We are facing the same Issue with german Umlauts in the Full AD Name. I can't tell if Umlauts in the login name work but if someone has the Login "Benjamin" and his full name is "Benjamin Blümchen" ist doesn't work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
