[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Nico K. commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Thanks to Daniel Beck and all who worked on this! 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] [swarm] (JENKINS-7543) Set tool locations from Swarm plugin CLI
cecom commented on JENKINS-7543 Set tool locations from Swarm plugin CLI I need that feature so hard... 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt commented on JENKINS-24244 Scheduled polling not run Well, that might be my bad. I just copied the relevant part of the log. I really should have mentioned that ... the log is quite large and does contain cron checking 20-8-14 2:03 the hudson.triggers.SCMTrigger is completely empty. what is the next step to do to help you guys get the right info? 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] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok created JENKINS-24361 NullPointerException when trying to log in Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory Created: 21/Aug/14 7:00 AM Description: When I try to login using the AD plugin, I get a NullPointerException (see below). I'm not sure if that was triggered by an update, since I don't login very often, but I was able to login successfully about a week ago using the same setup. Stack trace: java.lang.NullPointerException at java.lang.String$CaseInsensitiveComparator.compare(String.java:1228) at java.lang.String$CaseInsensitiveComparator.compare(String.java:1221) at java.lang.String.compareToIgnoreCase(String.java:1271) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) at jenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) at jenkins.model.IdStrategy.equals(IdStrategy.java:78) at hudson.model.User.getOrCreate(User.java:393) at hudson.model.User.getAll(User.java:475) at hudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) at hudson.model.User.get(User.java:358) at hudson.model.User.get(User.java:331) at hudson.model.User.get(User.java:438) at hudson.plugins.active_directory.ActiveDirectoryUserDetail.getJenkinsUser(ActiveDirectoryUserDetail.java:92) at hudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:103) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:299) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:196) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:140) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at
[JIRA] [core] (JENKINS-24362) Multiple NPE after 1.576 upgrade
gquerret created JENKINS-24362 Multiple NPE after 1.576 upgrade Issue Type: Bug Assignee: Unassigned Components: core Created: 21/Aug/14 7:15 AM Description: Since upgrading to 1.576 (from 1.561 IIRC), I'm getting NPE on different pages. When I trigger a specific job, I'm getting the following stacktrace : FATAL: null java.lang.NullPointerException at java.lang.String$CaseInsensitiveComparator.compare(String.java:1177) at java.lang.String$CaseInsensitiveComparator.compare(String.java:1170) at java.lang.String.compareToIgnoreCase(String.java:1220) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) at jenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) at jenkins.model.IdStrategy.equals(IdStrategy.java:78) at hudson.model.User.getOrCreate(User.java:393) at hudson.model.User.getAll(User.java:475) at hudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) at hudson.model.User.get(User.java:358) at hudson.model.User.get(User.java:331) at hudson.model.User.get(User.java:438) at hudson.model.Cause$UserIdCause.getUserName(Cause.java:413) at hudson.model.Cause$UserIdCause.print(Cause.java:423) at hudson.model.StreamBuildListener.started(StreamBuildListener.java:74) at hudson.model.Run.execute(Run.java:1725) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:233) As the stacktrace is about users, I went to the Jenkins users page. Only a limited set is displayed (as expected), but the full list (/asynchPeople) display : javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at
[JIRA] [core] (JENKINS-24362) Multiple NPE after 1.576 upgrade
gquerret commented on JENKINS-24362 Multiple NPE after 1.576 upgrade Seems identical to JENKINS-24317. You can probably close issue as duplicate. 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] [core] (JENKINS-24362) Multiple NPE after 1.576 upgrade
gquerret commented on JENKINS-24362 Multiple NPE after 1.576 upgrade In the users directory, I've renamed upper-case names to lower-case. Everything is working correctly now. 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] [core] (JENKINS-24362) Multiple NPE after 1.576 upgrade
gquerret resolved JENKINS-24362 as Duplicate Multiple NPE after 1.576 upgrade Change By: gquerret (21/Aug/14 7:28 AM) Status: Open Resolved Resolution: Duplicate 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
R. H. commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Great i hope i takes not so much time to implement it and build a new version. 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] [tfs] (JENKINS-22445) Creating workspace does not work if Update is checked
Karl-Heinz Marbaise commented on JENKINS-22445 Creating workspace does not work if Update is checked So this a problem of TFS itself not of the plugin. If yes you can close the issue, cause in this case it can't be solved by the plugin. 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] [tfs] (JENKINS-20041) Allow the TFS username and password to be stored globally
Karl-Heinz Marbaise commented on JENKINS-20041 Allow the TFS username and password to be stored globally That would be great. Otherwise you need to store the password in the Job DSL which means to store a password within a version control which is not a good idea. Or using a kind of template project where to get the password from. 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt edited a comment on JENKINS-24244 Scheduled polling not run Setting the hudson.triggers.Trigger log to FINER shows indeed: ... cron checking 20-8-14 2:03 ... aug 20, 2014 2:03:01 PM FINE hudson.triggers.Trigger cron checking hudson.model.FreeStyleProject@64ae3cef[Build STABLE] with spec ‘H 3 * * 1-6’ aug 20, 2014 2:02:01 PM FINER hudson.triggers.Trigger did not trigger hudson.model.FreeStyleProject@64ae3cef[Build STABLE] ... enter/leaving the cron schedule field in config shows the correct info (I've translated it to EN): Would last have run at Wednesday August 20 2014 3:00:08 CEST; would next run at Thursday 21 August 2014 3:00:08 CEST. I'll check for the hudson.triggers.SCMTrigger logging tomorrow (do not want to change the cron spec; might have something to to with the issue) 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] [tfs] (JENKINS-24363) Removed workspace of a job if already deleted on file system results in Crash
Karl-Heinz Marbaise created JENKINS-24363 Removed workspace of a job if already deleted on file system results in Crash Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 21/Aug/14 8:00 AM Description: If you try to delete a job via Jenkins UI where the workspace already has been deleted which means the worspace folder does not exist anymore the complete deletion will fail with an exception. A solution is to create an emptry workspace folder and delete afterwards. Project: Jenkins Priority: Critical Reporter: Karl-Heinz Marbaise 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] [core] (JENKINS-24299) Maven project build fails to terminate hanging build process
Tobias Oberlies commented on JENKINS-24299 Maven project build fails to terminate hanging build process The OOM/PermGen happens in the forked Maven build process. So you need to set something like -XX:MaxPermSize=32m in the MAVEN_OPTS to provoke the OOM there. 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] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok
updated JENKINS-24361
NullPointerException when trying to log in
Change By:
Matthias Uschok
(21/Aug/14 8:28 AM)
Description:
WhenItrytologinusingtheADplugin,IgetaNullPointerException(seebelow).Imnotsureifthatwastriggeredbyanupdate,sinceIdontloginveryoften,butIwasabletologinsuccessfullyaboutaweekagousingthesamesetup.Stacktrace:{
{
quote}
java.lang.NullPointerException atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1228) atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1221) atjava.lang.String.compareToIgnoreCase(String.java:1271) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) atjenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) atjenkins.model.IdStrategy.equals(IdStrategy.java:78) athudson.model.User.getOrCreate(User.java:393) athudson.model.User.getAll(User.java:475) athudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) athudson.model.User.get(User.java:358) athudson.model.User.get(User.java:331) athudson.model.User.get(User.java:438) athudson.plugins.active_directory.ActiveDirectoryUserDetail.getJenkinsUser(ActiveDirectoryUserDetail.java:92) athudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:103) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:299) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:196) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:140) atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
[JIRA] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok
updated JENKINS-24361
NullPointerException when trying to log in
Change By:
Matthias Uschok
(21/Aug/14 8:28 AM)
Description:
WhenItrytologinusingtheADplugin,IgetaNullPointerException(seebelow).Imnotsureifthatwastriggeredbyanupdate,sinceIdontloginveryoften,butIwasabletologinsuccessfullyaboutaweekagousingthesamesetup.Stacktrace:
{{
java.lang.NullPointerException atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1228) atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1221) atjava.lang.String.compareToIgnoreCase(String.java:1271) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) atjenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) atjenkins.model.IdStrategy.equals(IdStrategy.java:78) athudson.model.User.getOrCreate(User.java:393) athudson.model.User.getAll(User.java:475) athudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) athudson.model.User.get(User.java:358) athudson.model.User.get(User.java:331) athudson.model.User.get(User.java:438) athudson.plugins.active_directory.ActiveDirectoryUserDetail.getJenkinsUser(ActiveDirectoryUserDetail.java:92) athudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:103) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:299) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:196) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:140) atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
[JIRA] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok commented on JENKINS-24361 NullPointerException when trying to log in Might be related to https://issues.jenkins-ci.org/browse/JENKINS-22759 I get a similar Error/Stacktrace when I try to access "people" (jenkins/asynchPeople/) 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] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok commented on JENKINS-24361 NullPointerException when trying to log in Seems to be a jenkins issue. Accessing "people" triggers the error even when I completely remove the plugin. 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] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok commented on JENKINS-24361 NullPointerException when trying to log in Also happens when I try to run build jobs: FATAL: null java.lang.NullPointerException at java.lang.String$CaseInsensitiveComparator.compare(String.java:1228) at java.lang.String$CaseInsensitiveComparator.compare(String.java:1221) at java.lang.String.compareToIgnoreCase(String.java:1271) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) at hudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) at jenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) at jenkins.model.IdStrategy.equals(IdStrategy.java:78) at hudson.model.User.getOrCreate(User.java:393) at hudson.model.User.getAll(User.java:475) at hudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) at hudson.model.User.get(User.java:358) at hudson.model.User.get(User.java:331) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:266) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:327) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:689) at hudson.model.Run.execute(Run.java:1765) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:233) 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] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok
updated JENKINS-24361
NullPointerException when trying to log in
Change By:
Matthias Uschok
(21/Aug/14 8:46 AM)
Description:
WhenItrytologinusingtheADplugin,IgetaNullPointerException(seebelow).Imnotsureifthatwastriggeredbyanupdate,sinceIdontloginveryoften,butIwasabletologinsuccessfullyaboutaweekagousingthesamesetup.
Imusingthehttp://pkg.jenkins-ci.org/debianrepository
Stacktrace:{quote}java.lang.NullPointerException atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1228) atjava.lang.String$CaseInsensitiveComparator.compare(String.java:1221) atjava.lang.String.compareToIgnoreCase(String.java:1271) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:40) athudson.util.CaseInsensitiveComparator.compare(CaseInsensitiveComparator.java:34) atjenkins.model.IdStrategy$CaseInsensitive.compare(IdStrategy.java:160) atjenkins.model.IdStrategy.equals(IdStrategy.java:78) athudson.model.User.getOrCreate(User.java:393) athudson.model.User.getAll(User.java:475) athudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:903) athudson.model.User.get(User.java:358) athudson.model.User.get(User.java:331) athudson.model.User.get(User.java:438) athudson.plugins.active_directory.ActiveDirectoryUserDetail.getJenkinsUser(ActiveDirectoryUserDetail.java:92) athudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:103) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:299) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:196) athudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:140) atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
[JIRA] [active-directory] (JENKINS-24361) NullPointerException when trying to log in
Matthias Uschok commented on JENKINS-24361 NullPointerException when trying to log in Downgrade to jenkins 1.575 helps \o/ 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] [mask-passwords] (JENKINS-21690) Hide passwords in source code of jobs configuration page
Gregory SSI-YAN-KAI commented on JENKINS-21690 Hide passwords in source code of jobs configuration page I've also noticed that the password is visible in clear text when you go to the environment variables of a build: JENKINS_URL/job/JOB_NAME/BUILD_NUMBER/injectedEnvVars 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Tom FENNELLY commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL @Denis Duh... you are totally right. Sorry about that. That just goes to prove that it's not a good idea making changes late at night... better to rest the brain Thanks for covering me Denis !!! I'll fix it ASAP. 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
SCM/JIRA link daemon commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/task.jelly http://jenkins-ci.org/commit/jenkins/3daa6a97b02635d672e7646e83edb93abf50db06 Log: Readd static resource path for task icons JENKINS-24316 Missed this in previous commit - bad idea making even small changes late at night 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Tim Brust commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Looks good at my Jenkins again Thanks for the quick fix. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Guillaume commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb This is the output in my case: [android] Using Android SDK: /Users/build/.jenkins/tools/android-sdk $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 5874 * * daemon started successfully * $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /Users/build/.jenkins/tools/android-sdk/tools/emulator -no-boot-anim -ports 5872,5873 -avd hudson_de-DE_480_1200x1920_android-18_armeabi-v7a -no-snapshot-load -no-snapshot-save -no-window $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 [android] Waiting for emulator to finish booting... $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 offline [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete error: device offline error: device offline $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 offline [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete error: device offline error: device offline $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb disconnect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb disconnect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb connect emulator-5872 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb devices -l List of devices attached emulator-5872 device product:sdk model:sdk device:generic [android] adb devices returned 0 $ /Users/build/.jenkins/tools/android-sdk/platform-tools/adb -s emulator-5872 shell getprop dev.bootcomplete $
[JIRA] [core] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer created JENKINS-24364 Cannot Delete Job Item for Shared SCM settings Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Aug/14 9:59 AM Description: GIVEN: a job located in a folder structure using a SCM configuration of a different job in the same folder structure (specified with somefolder/somefolder/job) WHEN: try to delete the job THEN: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [core] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer commented on JENKINS-24364 Cannot Delete Job Item for Shared SCM settings WORKAROUND: setting the SCM configuration to NONE will allow to delete the job 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] [cloudbees-folder] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer updated JENKINS-24364 Cannot Delete Job Item for Shared SCM settings Change By: Thomas Fürer (21/Aug/14 10:02 AM) Component/s: cloudbees-folder Component/s: scm-api 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
dogfood commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Integrated in jenkins_main_trunk #3638 Readd static resource path for task icons JENKINS-24316 (Revision 3daa6a97b02635d672e7646e83edb93abf50db06) Result = SUCCESS tom.fennelly : 3daa6a97b02635d672e7646e83edb93abf50db06 Files : core/src/main/resources/lib/layout/task.jelly 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] [ldap] (JENKINS-24347) LDAP advanced parameters not taken in account for initial verification request
François Thieke commented on JENKINS-24347 LDAP advanced parameters not taken in account for initial verification request thank you for your answer i´m not speaking of the initial configuration but of editing a working configuration. so all values should be defined fine. i guess it might be a timing issue where the request is triggered before the managerDN value is assigned to the form field. i didn´t check the code but it sounds plausible to me that, while looping through all currend values that have to be assigned the form fields, the verification request is triggered as soon as the server url value is assigned, while the managerDN value yet isn´t. so the method that generates the url to be requestet reads the value out of the managerDN field that is still empty. in this case the solution would be to delay the generation of the request url to a point where all values where assigned to their form fields. in reference to your suggested workaround it would probably also solve our problem to simply reverse the loop that assignes the initial form values, so that the managerDN field is filled before the url field. on the other hand this could affect other requests that might rely on the current assignment order. also i guess it would mask the issue to trigger the verification request when the managerDN value is assigned as well. this should result in two requests where the first failes while the second is successful and thereby hides the fail of the first attempt. you might want to consider doing so anyway as this would also result in reflecting changes done to the managerDN field. as right now the changes done to managerDN are not "live-tested" in the way that changes to the url it self are. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb @Guillaume that output shows that the emulator is starting up and is correctly attaching to adb. For some reason the emulator is then failing to complete the boot. I think your scenario should be tracked as a separate issue (to avoid things getting too complex). I guess that the build will not have captured any logcat output before failure. The next step in debugging your problem might be to capture it and see if there is anything of interest in the logs. 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] [view-job-filters] (JENKINS-24365) View job filter regular expression does not work
Ben Franklin
created JENKINS-24365
View job filter regular _expression_ does not work
Issue Type:
Bug
Assignee:
Jacob Robertson
Components:
view-job-filters
Created:
21/Aug/14 10:23 AM
Description:
When using the Regular _expression_ Job Filter a simple _expression_ like publish* entered into the Regular _expression_ text box does not return any jobs with name starting with 'publish'.
This is when using Match Value of 'Job name' and Match Type 'Included Matched'.
In fact it only seems to work when you enter the exact name of a job into the Regular _expression_.
Also get the following error when entering *publish into the Regular _expression_ texbox:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.views.RegExJobFilter from {"regex":"*publish*","valueTypeString":"NAME","includeExcludeTypeString":"includeMatched","stapler-class":"hudson.views.RegExJobFilter","kind":"hudson.views.RegExJobFilter"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] [role-strategy] (JENKINS-19934) Add Job Create permission to project roles
mwebber reopened JENKINS-19934 Add Job Create permission to project roles "Job Create" can now be selected (or de-delected) for a jobname pattern in "Manage and Assign Roles" -- "Manage Roles" -- "Project roles". However, this doesn't appear to have aby effect: If a user has a global role with "Job Create" then they can create any jobname. If the user does not have such a global role, they cannot create any jobs. In fact, the "New View" link to create a job is not even displayed. Project roles are ignored. Is there some change in Jenkins core that needs to be made to actually use the "Project roles" "Job Create" setting? If so, is there a Jira ticket for this, or does one need to be opened? Thanks Change By: mwebber (21/Aug/14 10:31 AM) Resolution: Fixed Status: Resolved Reopened 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] [role-strategy] (JENKINS-19934) Add Job Create permission to project roles
Oleg Nenashev commented on JENKINS-19934 Add Job Create permission to project roles 1) As designed. Global roles override any project-specific permissions 2) See https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin?focusedCommentId=73533281#comment-73533281 for configuration guidelines 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] [copyartifact] (JENKINS-9709) Feature to copy artifact from different upstream projects
Serhiy Hapiy commented on JENKINS-9709 Feature to copy artifact from different upstream projects Our workaround is to invoke the downstream build using the Parametrized Trigger plugin. We pass the upstream project name as a parameter. But we cannot use "Build after other projects..." approach in this case, which results in increased complexity of configurations. 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] [perforce] (JENKINS-24366) Missing Root in client spec
Morne Joubert created JENKINS-24366 Missing Root in client spec Issue Type: Bug Assignee: Rob Petti Attachments: missing_root.png Components: perforce Created: 21/Aug/14 11:05 AM Description: In our logs I can see many lines such as the ones below: Problem: Error in client specification. Missing required field 'Root'. For Command: /u-blox/gallery/perforce/p4/lin_64/2014.1/bin/p4 -P CB36E3E1DC213D9D0161CA6FF7C5309B -s client -S //l1phy/main_l1phy -i With Data: === Client: main_mlb_full_split_stack_build_jenkins_mlb-2062542078 Description: Root: Options: noallwrite clobber nocompress unlocked nomodtime rmdir LineEnd: local Stream: //l1phy/main_l1phy When looking at the client spec (see image) i can see a Root specified Project: Jenkins Priority: Major Reporter: Morne Joubert 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] [core] (JENKINS-24244) Scheduled polling not run
Daniel Beck commented on JENKINS-24244 Scheduled polling not run While you should follow the advice by Jesse and install Support Core, the following will make it easier to access older log messages: Try setting the System property hudson.util.RingBufferLogHandler.defaultSize to a large value. Change the Jenkins java call (if using bundled Jetty container) to add it like so: java -Dhudson.util.RingBufferLogHandler.defaultSize=1 -jar jenkins.war Then the UI will show more messages. Requires a full restart of Jenkins, and not via /safeRestart. Shut it down, then start again. The log entries that are relevant are those logged between 2:59 and 3:05 or so. The rest is expected to not matter. "did not trigger" is expected every minute of every day, except at 3. There's this weird behavior in Jenkins that skips any SCM polling while Jenkins is in "quiet down" mode (the red banner "Jenkins is preparing to shut down"). Make sure you're not in this mode (one of the backup plugins does this IIRC) at the scheduled time. 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Richard Mortimer commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Tested with latest git and the images are now properly displayed including the /static/ prefix to help with caching. Thanks. 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] [view-job-filters] (JENKINS-24365) View job filter regular expression does not work
Jacob Robertson resolved JENKINS-24365 as Not A Defect View job filter regular _expression_ does not work Change By: Jacob Robertson (21/Aug/14 11:25 AM) Status: Open Resolved Resolution: NotADefect 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] [view-job-filters] (JENKINS-24365) View job filter regular expression does not work
Jacob Robertson commented on JENKINS-24365 View job filter regular _expression_ does not work Please google "regular _expression_ syntax" "publish*" matches publishhh but not publish1 "*publish is an invalid regex" 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb A reason for the emulator not starting properly could be the high screen resolution. The emulator does not generally deal with this well, and the window server and various system services tend to go into an endless loop of crashing and restarting. So I would also try with a smaller screen resolution, and maybe lower screen density. We can't do much about the emulator being crappy, but maybe in these cases we should also (somehow) archive the logcat output (or instruct the user how to see the live logcat, or scan the log for system crashes) to better debug startup issues. 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] [perforce] (JENKINS-24366) Missing Root in client spec
Morne Joubert updated JENKINS-24366 Missing Root in client spec Change By: Morne Joubert (21/Aug/14 11:30 AM) Description: InourlogsIcanseemanylinessuchastheonesbelow:Problem:Errorinclientspecification.MissingrequiredfieldRoot.ForCommand:/u-blox/gallery/perforce/p4/lin_64/2014.1/bin/p4-PCB36E3E1DC213D9D0161CA6FF7C5309B-sclient-S//l1phy/main_l1phy-iWithData:===Client:main_mlb_full_split_stack_build_jenkins_mlb-2062542078Description:Root:Options:noallwriteclobbernocompressunlockednomodtimermdirLineEnd:localStream://l1phy/main_l1phyWhenlookingattheclientspec(seeimage)icanseeaRootspecified . Iamnotsureifthisiscausinganyproblemsbutsomethingmustbecausingthis 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Yeah, I tried the same config as Guillaume above, and got the same failure to boot. I ran this on my Jenkins slave while waiting for the emulator startup to time-out: ANDROID_ADB_SERVER_PORT=5829 ~/jenkins/tools/android-sdk/platform-tools/adb logcat There I saw a loop of /system/bin/surfaceflinger native crashes. 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] [core] (JENKINS-24244) Scheduled polling not run
Rick Oosterholt commented on JENKINS-24244 Scheduled polling not run There's this weird behavior in Jenkins that skips any SCM polling while Jenkins is in "quiet down" mode (the red banner "Jenkins is preparing to shut down"). Make sure you're not in this mode (one of the backup plugins does this IIRC) at the scheduled time. That's it! I'm using Exclusive Execution Plugin which puts Jenkins in "shutdown mode". Thanks for your help! Has anyone an idea to ensure a specific project is executed "exclusively" in Jenkins? 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] [core] (JENKINS-24244) Scheduled polling not run
Daniel Beck updated JENKINS-24244 Scheduled polling not run Change By: Daniel Beck (21/Aug/14 11:55 AM) Status: Reopened Open 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] [performance-plugin] (JENKINS-24367) Performance plugin report files url should allow for parameter substitution
Maciej Nabozny
created JENKINS-24367
Performance plugin report files url should allow for parameter substitution
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Manuel Carrasco
Attachments:
2014-08-21_1354.png
Components:
performance-plugin
Created:
21/Aug/14 11:55 AM
Description:
I'm expecting parameters to be allowed when setting
**/${jmeterScript}.jtl
in Report files url field
see screenshot
Project:
Jenkins
Priority:
Major
Reporter:
Maciej Nabozny
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] [core] (JENKINS-24244) Scheduled polling not run
Daniel Beck resolved JENKINS-24244 as Not A Defect Scheduled polling not run Not a defect, as brain dead as the current polling behavior is. (My own Jenkins builds remove that part as it's too annoying.) Please direct further questions to the jenkinsci-users list, or #jenkins on Freenode. Change By: Daniel Beck (21/Aug/14 11:57 AM) Status: Open Resolved Resolution: NotADefect 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Jesse Glick assigned JENKINS-24317 to Jesse Glick Nullpointer Exception on build in version 1.576 cant see output and fails Change By: Jesse Glick (21/Aug/14 12:02 PM) Assignee: DanielBeck JesseGlick 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] [template-project] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Daniel Beck updated JENKINS-24364 Cannot Delete Job Item for Shared SCM settings Issue appears to be caused by Template Project. Change By: Daniel Beck (21/Aug/14 12:03 PM) Component/s: template-project Component/s: core Component/s: scm-api Component/s: cloudbees-folder 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-18935) Make Subversion plugin support Subversion 1.8
Van Lewis commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 No support for the 1.8 subversion client is affecting the upgrade to ankhsvn and tortoisesvn impacting the use of Visual Studio 2013. 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] [maven] (JENKINS-24360) Jenkins Dashboard issue after creating Pipeline view.
Daniel Beck updated JENKINS-24360 Jenkins Dashboard issue after creating Pipeline view. Looks like an issue of Maven Project plugin or Violations plugin, so assigning to those for now. Change By: Daniel Beck (21/Aug/14 12:06 PM) Component/s: maven Component/s: violations Component/s: core 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Shannon Kerr commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL I can confirm the same. My sandbox Jenkins is now functioning normally. Thanks for the quick fix implementation Tom FENNELLY. We all succumb to late night work bugs every once in a while. 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] [git-client] (JENKINS-22400) Git timeout on other actions than fetch/clone
Mark Waite updated JENKINS-22400 Git timeout on other actions than fetch/clone Change By: Mark Waite (21/Aug/14 12:19 PM) Status: Reopened Open 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Flavio Donzé created JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-client Created: 21/Aug/14 12:20 PM Description: Getting the following error after updating GIT plugin: 1.5.0 2.2.5 GIT client plugin: 1.3.0 1.10.1 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:/Progra~2/Git/bin/git.exe fetch --tags --progress https://usern...@bitbucket.org/project/repository.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: fatal: Authentication failed for 'https://usern...@bitbucket.org/project/repository.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1195) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:266) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:422) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:857) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:890) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) at hudson.model.AbstractProject.checkout(AbstractProject.java:1255) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:233) Project: Jenkins Priority: Major Reporter: Flavio Donzé 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite commented on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git I believe you'll need to switch from using the https://usern...@bitbucket.org/ syntax to use a credential defined through "Manage Credentials" and the format https://bitbucket.org/ syntax. 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite edited a comment on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git I believe you'll need to switch from using the https://usern...@bitbucket.org/ syntax to use a credential defined through "Manage Credentials" and the https://bitbucket.org/ syntax (without the username@ part). 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] [core] (JENKINS-23872) Jenkins users disappeared!
SCM/JIRA link daemon commented on JENKINS-23872 Jenkins users disappeared! Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java test/src/test/resources/hudson/model/UserTest/migration.zip http://jenkins-ci.org/commit/jenkins/088edabb31a90cd607f3c6a3123effce5703c817 Log: FIXED JENKINS-24317 Corrected user dir migration code from JENKINS-23872. Adapted from #1375 by @daniel-beck: omitting change to User construction, and adding test. Compare: https://github.com/jenkinsci/jenkins/compare/3daa6a97b026...088edabb31a9 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
SCM/JIRA link daemon commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java test/src/test/resources/hudson/model/UserTest/migration.zip http://jenkins-ci.org/commit/jenkins/088edabb31a90cd607f3c6a3123effce5703c817 Log: FIXED JENKINS-24317 Corrected user dir migration code from JENKINS-23872. Adapted from #1375 by @daniel-beck: omitting change to User construction, and adding test. Compare: https://github.com/jenkinsci/jenkins/compare/3daa6a97b026...088edabb31a9 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
SCM/JIRA link daemon commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java test/src/test/resources/hudson/model/UserTest/migration.zip http://jenkins-ci.org/commit/jenkins/bce92ec53ddefb7d5105f3f82af96ee954467bdd Log: FIXED JENKINS-24317 Corrected user dir migration code from JENKINS-23872. Adapted from #1375 by @daniel-beck: omitting change to User construction, and adding test. (cherry picked from commit 088edabb31a90cd607f3c6a3123effce5703c817) Conflicts: changelog.html 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Jesse Glick resolved JENKINS-24317 as Fixed Nullpointer Exception on build in version 1.576 cant see output and fails Fixing in trunk, and backporting to rc so it goes into 1.577 as well. Change By: Jesse Glick (21/Aug/14 12:45 PM) Status: InProgress Resolved Resolution: Fixed 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] [core] (JENKINS-23872) Jenkins users disappeared!
SCM/JIRA link daemon commented on JENKINS-23872 Jenkins users disappeared! Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java test/src/test/resources/hudson/model/UserTest/migration.zip http://jenkins-ci.org/commit/jenkins/bce92ec53ddefb7d5105f3f82af96ee954467bdd Log: FIXED JENKINS-24317 Corrected user dir migration code from JENKINS-23872. Adapted from #1375 by @daniel-beck: omitting change to User construction, and adding test. (cherry picked from commit 088edabb31a90cd607f3c6a3123effce5703c817) Conflicts: changelog.html 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-24369) How to configure Subversion Plugin to checkout into custom work space
Sana Ahmad created JENKINS-24369 How to configure Subversion Plugin to checkout into custom work space Issue Type: Bug Assignee: Unassigned Components: subversion Created: 21/Aug/14 12:46 PM Description: I want to configure my job with subversion 1.7. I have been using TortoiseSVN for version controlling on my system. Now I want to automate build process of my .net project using MSBuild, where i want to perform following steps: 1. Scheduling my build process for after every 2 hours 1. Subversion Checkout latest code from the repository (URL) into two different local directories on my system 2. Build process starts according to given MSBuild version and .sln file. Major issue is how to provide two Repoistory URL under SCM-Subversion with each Local Module Directory set to absolute path on my system? Project: Jenkins Priority: Critical Reporter: Sana Ahmad 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Flavio Donzé commented on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git Thanks for this workaround, but I need to use the username@host syntax. 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] [core] (JENKINS-24361) NullPointerException when trying to log in
Daniel Beck resolved JENKINS-24361 as Duplicate NullPointerException when trying to log in Duplicates JENKINS-24317. Change By: Daniel Beck (21/Aug/14 12:48 PM) Status: Open Resolved Resolution: Duplicate 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] [core] (JENKINS-24361) NullPointerException when trying to log in
Daniel Beck updated JENKINS-24361 NullPointerException when trying to log in Change By: Daniel Beck (21/Aug/14 12:48 PM) Component/s: core Component/s: active-directory 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-24369) How to configure Subversion Plugin to checkout into custom work space
Daniel Beck resolved JENKINS-24369 as Not A Defect How to configure Subversion Plugin to checkout into custom work space JIRA is an issue tracker, not a support site. Ask somewhere else. Also, reports aren't critical just because you need an immediate answer. Change By: Daniel Beck (21/Aug/14 12:54 PM) Status: Open Resolved Resolution: NotADefect 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] [mailer] (JENKINS-24318) Restrict which domains mail is sent to
Daniel Beck resolved JENKINS-24318 as Duplicate Restrict which domains mail is sent to This just duplicates the linked issue. Change By: Daniel Beck (21/Aug/14 12:57 PM) Status: Open Resolved Resolution: Duplicate 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] [build-pipeline] (JENKINS-23749) Incomplete view configuration breaks all Jenkins views
Daniel Beck resolved JENKINS-23749 as Duplicate Incomplete view configuration breaks all Jenkins views Duplicates JENKINS-23363. Change By: Daniel Beck (21/Aug/14 1:00 PM) Status: Open Resolved Resolution: Duplicate 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL
Oliver Gondža created JENKINS-24370 Saving ownership redirects to absolute URL Issue Type: Bug Assignee: Oliver Gondža Components: ownership Created: 21/Aug/14 1:00 PM Description: Use domain relative address instead. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Dhwani Shah commented on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git I am also getting the same issue in version 1.576. What should i do connect with the bitbucket repository? 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] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Dhwani Shah edited a comment on JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git I am also getting the same issue in version 1.576. What should i do to connect with the bitbucket repository in the latest version? 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] [core] (JENKINS-24371) Neither dashboard nor build details work
Zdenek Vais created JENKINS-24371 Neither dashboard nor build details work Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Aug/14 1:27 PM Description: When I try to access Dashboard or go to any build details I get an error with following stack trace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-1.576.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-1.576.jar!/lib/hudson/projectView.jelly:67:24: d:invokeBody null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
thetaphi commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Hi, replaced my WAR from the Ubuntu/Debian package in /usr/share/jenkins by the latest snapshot build - works fine! Thanks! 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
SCM/JIRA link daemon commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/task.jelly test/src/test/java/lib/layout/IconTest.java test/src/test/resources/lib/layout/IconTest/01_testIcons.jelly test/src/test/resources/lib/layout/IconTest/03_testTask.jelly http://jenkins-ci.org/commit/jenkins/830a5e7f618a53a4ff3d1cad1127efc5fcc47601 Log: FIXED JENKINS-24316 Fixed unknown task icon src path construction (cherry picked from commit 286337ea39c0db6e056af61e616736bafc5f0581) 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
SCM/JIRA link daemon commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/task.jelly http://jenkins-ci.org/commit/jenkins/5b805fa16e240e3657a7f263eeef11281a393efa Log: Readd static resource path for task icons JENKINS-24316 Missed this in previous commit - bad idea making even small changes late at night (cherry picked from commit 3daa6a97b02635d672e7646e83edb93abf50db06) Compare: https://github.com/jenkinsci/jenkins/compare/bce92ec53dde...5b805fa16e24 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] [github-oauth] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Hans-Christian Otto commented on JENKINS-17539 Swarm clients fail to connect if GitHub for authentication I am having this issue as well. Any progress on it? 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] [github-oauth] (JENKINS-13354) Jenkins very slow when not an admin
alex rothenberg commented on JENKINS-13354 Jenkins very slow when not an admin I have submitted a github pull request https://github.com/jenkinsci/github-oauth-plugin/pull/27 and jira issue https://issues.jenkins-ci.org/browse/JENKINS-24069 intended to resolve this. The original slowness was also my fault and I'm sorry for that. It has to do with the number of github api calls it makes and the PR improves it to O(# of organizations user has access to) where it previously was O(# of jobs in jenkins). 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment
Kohsuke Kawaguchi created JENKINS-24372 Test runner should be able to specify the local *.hpi file to put into the test environment Issue Type: New Feature Assignee: Oliver Gondža Components: acceptance-test-harness Created: 21/Aug/14 1:42 PM Description: People should be able to test unreleased versions of the plugin with the acceptance test harness. Wiring script should be able to specify override from local file system. Also note that in this case, dependencies need to be obtained from manifest, not from update center metadata. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
dogfood commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Integrated in jenkins_main_trunk #3639 FIXED JENKINS-24317 Corrected user dir migration code from JENKINS-23872. (Revision 088edabb31a90cd607f3c6a3123effce5703c817) Result = SUCCESS Jesse Glick : 088edabb31a90cd607f3c6a3123effce5703c817 Files : core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java test/src/test/resources/hudson/model/UserTest/migration.zip changelog.html 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] [jira] (JENKINS-23292) jira-plugin uses emails from jira
Walter Kacynski commented on JENKINS-23292 jira-plugin uses emails from jira An example stack trace of trying to resolve emails when triggered from email-ext at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.login(JirasoapserviceV2SoapBindingStub.java:3797) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:240) at hudson.plugins.jira.JiraMailAddressResolver.findMailAddressFor(JiraMailAddressResolver.java:29) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:122) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:548) at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:110) at hudson.plugins.emailext.plugins.recipients.DevelopersRecipientProvider.addRecipients(DevelopersRecipientProvider.java:38) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:516) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) We use the LDAP plugin and email addresses are already resolved correctly and stored within the local Jenkins user profile. JIRA should not be contacted to perform email lookup. 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] [core] (JENKINS-24336) NullPointerException on login after upgrade to 1.576
Justin Chang commented on JENKINS-24336 NullPointerException on login after upgrade to 1.576 Downgrading back to 1.575 seems to fix the issue for me. 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] [core] (JENKINS-24371) Neither dashboard nor build details work
Zdenek Vais commented on JENKINS-24371 Neither dashboard nor build details work Pages as Build history, People or Manage Jenkins are working. Any idea what can be wrong? 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL
Oleg Nenashev started work on JENKINS-24370 Saving ownership redirects to absolute URL Change By: Oleg Nenashev (21/Aug/14 1:53 PM) Status: Open InProgress 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL
Oleg Nenashev commented on JENKINS-24370 Saving ownership redirects to absolute URL Are there any issues with absolute URLs in new core versions? 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] [github-oauth] (JENKINS-22035) Add Repository based authorization
alex rothenberg resolved JENKINS-22035 as Fixed Add Repository based authorization Closing - it was merged and release in v0.17 Change By: alex rothenberg (21/Aug/14 1:57 PM) Status: Open Resolved Resolution: Fixed 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] [changes-since-last-success] (JENKINS-24373) Changes - Links to Redmine Repo Browser don't work
Gerardo Valido created JENKINS-24373 Changes - Links to Redmine Repo Browser dont work Issue Type: Bug Assignee: Nicolas De Loof Components: changes-since-last-success Created: 21/Aug/14 1:58 PM Description: We are using Jenkins as CI and Redmine as repo browser. In the jenkins project we checkout http://svn/customer1/branch/server/1.11/product1 The root of this repo is http://svn/customer1/ In Redmine we also checked out http://svn/customer1/branch/server/1.11/product1 Jenkins creates the links in changes from the repo root like /branch/server/1.11/... These links don't work with the redmine repo browser as redmines svn project starts with product1. Project: Jenkins Priority: Minor Reporter: Gerardo Valido 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] [github-oauth] (JENKINS-22035) Add Repository based authorization
alex rothenberg commented on JENKINS-22035 Add Repository based authorization Closing this issues as it was merged and released in v0.17 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
SCM/JIRA link daemon commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/4c0cfe40c9ebbea81bf2b8a6931cda3513be1bfe Log: Noting RC merge of JENKINS-24316, JENKINS-24317 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
SCM/JIRA link daemon commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/4c0cfe40c9ebbea81bf2b8a6931cda3513be1bfe Log: Noting RC merge of JENKINS-24316, JENKINS-24317 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] [ownership] (JENKINS-23947) Make ownership injection default
Oleg Nenashev commented on JENKINS-23947 Make ownership injection default The feature would be useful, but we will have to replace the BuildWrapper to another mechanism. BTW, it is possible 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] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Daniel Beck commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL The fix will be in 1.577, scheduled to be released this weekend or so. 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] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Daniel Beck commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails The fix will be in 1.577, scheduled to be released this weekend or so. 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] [perforce] (JENKINS-24366) Missing Root in client spec
Rob Petti assigned JENKINS-24366 to Unassigned Missing Root in client spec Change By: Rob Petti (21/Aug/14 2:09 PM) Assignee: RobPetti 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] [ownership] (JENKINS-23926) Job Ownership not available if VCS fails
Oleg Nenashev commented on JENKINS-23926 Job Ownership not available if VCS fails I'll try that. thanks. Do you by chance know if one can set a default value nonetheless? I'll add the default value to token macros 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] [role-strategy] (JENKINS-19934) Add Job Create permission to project roles
mwebber commented on JENKINS-19934 Add Job Create permission to project roles Global roles override any project-specific permissions. Understood. My problem is when the user is not assigned to any global role. Here's the problem case: The main Jenkins configuration has "Restrict project naming" on, with "Role-Based Strategy" selected. I have a project role called "Controls-Administrator" with a jobname pattern of "Controls.*". The role has all job permissions set. user xzl80115 is not assigned to any global role user xzl80115 is assigned to project role "Controls-Administrator" In this case, I would expect that user xzl80115 could create jobs named something like "Controls_abc". However, the "New View" link to create a job is never displayed, and if the user manually enters the URL http://jenkins/newJob then he gets told he does not have permission to create any jobs. It may be relevant that users authenticate using the CAS plugin and the CAS 2.0 protocol. 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] [build-pipeline] (JENKINS-20841) Links of the pipeline view are not working for project using the Cloudbees folder plug-in
dserodio commented on JENKINS-20841 Links of the pipeline view are not working for project using the Cloudbees folder plug-in Gonzague's PR was merged and released in 1.4.3 but there are still some problems left (eg.: clicking on Run when the first job in the pipeline is parametrized gives a 404) 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] [perforce] (JENKINS-24366) Missing Root in client spec
Rob Petti commented on JENKINS-24366 Missing Root in client spec Provide details please. Where are you seeing these logs? What sort of job are you using? What OS? Jenkins version? Plugin version? 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] [plugin] (JENKINS-24374) java.util.zip.ZipException thrown when starting Jenkins using mvn hpi:run
Scott Hathaway created JENKINS-24374 java.util.zip.ZipException thrown when starting Jenkins using mvn hpi:run Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: pom.xml Components: plugin Created: 21/Aug/14 2:15 PM Description: While working on changes to the m2release plugin, I found that the .hli file being produced by the maven-hpi-plugin contained paths to .pom files in the Libraries section. This only became an issue when I moved the m2release plugin to the 1.532 version of Jenkins core as the updated ClassPluginStrategy class used the AntClassLoader and no longer the URLClassloader to load dependencies. Attempting to start Jenkins using mvn hpi:run resulted in a java.util.zip.ZipException. I fixed the issue and submitted a pull request to the maven-hpi-plugin project: https://github.com/jenkinsci/maven-hpi-plugin/pull/10 Repro: 1. Update the m2release plugin pom.xml parent to version 1.532. 2. Set the maven-plugin dependency to version 2.0. 3. Execute a mvn clean hpi:run Result: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:215) at java.util.zip.ZipFile.init(ZipFile.java:145) at java.util.jar.JarFile.init(JarFile.java:153) at java.util.jar.JarFile.init(JarFile.java:117) at org.apache.tools.ant.AntClassLoader.addPathFile(AntClassLoader.java:492) at hudson.ClassicPluginStrategy$AntClassLoader2.addPathFiles(ClassicPluginStrategy.java:665) at hudson.ClassicPluginStrategy.createClassLoader(ClassicPluginStrategy.java:227) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:202) at hudson.PluginManager$1$3$1.run(PluginManager.java:238) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Environment: Ubuntu 14.04, Maven 3.2.1, Jenkins 1.532 (Fails in current as well.) Project: Jenkins Priority: Major Reporter: Scott Hathaway 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment
SCM/JIRA link daemon resolved JENKINS-24372 as Fixed Test runner should be able to specify the local *.hpi file to put into the test environment Change By: SCM/JIRA link daemon (21/Aug/14 2:17 PM) Status: Open Resolved Resolution: Fixed 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.
