[JIRA] [jacoco-plugin] (JENKINS-25818) Next day after a Jenkins reboot the report is empty
podskalsky commented on JENKINS-25818 Next day after a Jenkins reboot the report is empty LOG error message during jenkins reboot: java.lang.NullPointerException at hudson.plugins.jacoco.report.CoverageReport.(CoverageReport.java:65) at hudson.plugins.jacoco.JacocoBuildAction.getResult(JacocoBuildAction.java:227) at hudson.plugins.jacoco.JacocoBuildAction.getTarget(JacocoBuildAction.java:200) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:674) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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 org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) at com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:88) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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.ChainedServl
[JIRA] [discard-old-build-plugin] (JENKINS-25819) Execute keepLastBuilds function should be an option
Félix Belzunce Arcos created JENKINS-25819 Execute keepLastBuilds function should be an option Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: discard-old-build-plugin Created: 28/Nov/14 7:52 AM Description: updateBuildsList calls keepLastBuilds by default what end up with the following builds no consider by the plugin for all the option running in perform: if (r.isBuilding()) continue; if (r == lastBuild) continue; if (r == lastCompletedBuild) continue; if (r == lastFailedBuild) continue; if (r == lastStableBuild) continue; if (r == lastSuccessfulBuild) continue; if (r == lastUnstableBuild) continue; if (r == lastUnsuccessfulBuild) continue; newList.add(r); } This might be an optional as is quite confusing as you can end up specifying you want `Max of builds to keep=X`, but then have in the build history X+DELTA. Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos 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] [jacoco-plugin] (JENKINS-25818) Next day after a Jenkins reboot the report is empty
podskalsky updated JENKINS-25818 Next day after a Jenkins reboot the report is empty Change By: podskalsky (28/Nov/14 7:48 AM) Summary: Next day after build a Jenkins reboot the report is empty Description: After a Build there the report is OK.But next day after a nigthly jenkins reboot the build the report is empty! (The graph at the job page is still there but when i go into details there is nothing)At night we always have a server reboot.Maybe the Log Rotation is the problem? If I reboot during the day the report is also empty. 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] [jacoco-plugin] (JENKINS-25818) Next day after build the report is empty
podskalsky created JENKINS-25818 Next day after build the report is empty Issue Type: Bug Assignee: Ognjen Bubalo Attachments: 2014-11-28 08_17_51-Jenkins.png, 2014-11-28 08_19_14-OTTV.CCF.V1.0 Config [Jenkins].png, 2014-11-28 08_29_51-Jenkins.png, 2014-11-28 08_32_50-OTTV.CCF.V1.0 [Jenkins].png Components: jacoco-plugin Created: 28/Nov/14 7:35 AM Description: After Build there report is OK. But next day after the build the report is empty! (The graph at the job page is still there but when i go into details there is nothing) At night we always have a server reboot. Maybe the Log Rotation is the problem? Environment: Latest Jekins v. 1.590 Latest Jacoco Plugin 1.0.17 Project: Jenkins Priority: Critical Reporter: podskalsky 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] [multijob-plugin] (JENKINS-25817) Improve multijob plugin to restart tasks from failed subjob
Viachaslau Kabak created JENKINS-25817 Improve multijob plugin to restart tasks from failed subjob Issue Type: Improvement Assignee: Unassigned Components: multijob-plugin Created: 28/Nov/14 7:33 AM Description: If one sub-job fails we need to restart this job manually and then start next sub-jobs manually too. Or start multijob again. I suggest to improve multijob flexibility: to start multijob from any of sub-jobs: it starts chosen sub-job and next subjobs. It will help to save time if some job fails and we need to continue building after some fixes. Project: Jenkins Priority: Major Reporter: Viachaslau Kabak 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] [remoting] (JENKINS-25816) Race condition in Proc.join during Channel.syncIO exchange
Arcadiy Ivanov created JENKINS-25816 Race condition in Proc.join during Channel.syncIO exchange Issue Type: Bug Assignee: Unassigned Components: remoting Created: 28/Nov/14 7:21 AM Description: Slave: "pool-1-thread-7 for channel / waiting for hudson.remoting.Channel@59494225:channel" #31 prio=5 os_prio=0 tid=0x7f197c018800 nid=0xb40 in Object.wait() [0x7f19c8f0b000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) - locked <0xeb2b82b0> (a hudson.remoting.UserRequest) at hudson.remoting.Channel.call(Channel.java:742) at hudson.remoting.Channel.syncIO(Channel.java:1224) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1120) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) "Channel reader thread: channel" #14 prio=5 os_prio=0 tid=0x7f19f4349800 nid=0xb2e runnable [0x7f19c9506000] java.lang.Thread.State: RUNNABLE at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:246) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read(BufferedInputStream.java:265) - locked <0xc0018040> (a java.io.BufferedInputStream) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Master: "Executor #0 for Primary Koji Slave Build Machine (i-6fa7f885) : executing WildFly - WildFly Distro #39 / waiting for hudson.remoting.Channel@30bd27ca:Primary Koji Slave Build Machine (i-6fa7f885)" #9336 daemon prio=5 os_prio=0 tid=0x2acaa84b6000 nid=0x14268 in Object.wait() [0x2acad238f000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) - locked <0x0007bf395350> (a hudson.remoting.UserRequest) at hudson.remoting.Channel.call(Channel.java:742) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy84.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) at hudson.Launcher$ProcStarter.join(Launcher.java:367) at org.jfrog.hudson.maven3.Maven3Builder.perform(Maven3Builder.java:85) at hudso
[JIRA] [rebuild-plugin] (JENKINS-25815) Rebuild plugin doesn't load all Parameters
Sanketh PB updated JENKINS-25815 Rebuild plugin doesn't load all Parameters Change By: Sanketh PB (28/Nov/14 4:38 AM) Description: Say there are two parameters in the job PARAM1, PARAM2. These parameters are loaded in the Rebuild page as expected on Rebuild. If the Job adds PARAM3 and PARAM4 dynamically using ParametersAction then PARAM3 and PARAM4 are not loaded.We want the all PARAMETERS to be reloaded in Rebuild page to preserve few settings in rebuild. It would really help if all available Parameters are reloaded 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] [rebuild-plugin] (JENKINS-25815) Rebuild plugin doesn't load all Parameters
Sanketh PB created JENKINS-25815 Rebuild plugin doesn't load all Parameters Issue Type: Bug Assignee: ragesh_nair Components: rebuild-plugin Created: 28/Nov/14 4:37 AM Description: Say there are two parameters in the job PARAM1, PARAM2. These parameters are loaded in the Rebuild page as expected on Rebuild. If the Job adds PARAM3 and PARAM4 dynamically using ParametersAction then PARAM3 and PARAM4 are not loaded. We want the all PARAMETERS to be reloaded in Rebuild page to preserve few settings in rebuild. Environment: Jenkins Version 1.565.2 / 1.590 Parameterized-Trigger plugin 2.25 Rebuild plugin 1.22 Project: Jenkins Priority: Critical Reporter: Sanketh PB 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-plugin] (JENKINS-10024) Capture video stream from the emulator window during test and store as artifact
Dimitri Tenenbaum commented on JENKINS-10024 Capture video stream from the emulator window during test and store as artifact Take a look at VncRecorder Plugin, it uses vnc2swf and stores video file es an artifact: https://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+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] [android-emulator-plugin] (JENKINS-10024) Capture video stream from the emulator window during test and store as artifact
Dimitri Tenenbaum edited a comment on JENKINS-10024 Capture video stream from the emulator window during test and store as artifact Take a look at VncRecorder Plugin, it uses vnc2swf and stores video file as an artifact: https://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+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] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
Paul Eipper commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Still happening here. @kutzi: what do you think about @cforce suggestion? 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Daniel Beck commented on JENKINS-25807 Is this plugin still maintained? The only developer to work on the plugin since 2009 has made the last change in April 2011, and has never done anything in this tracker (volkai). Given that, and that there's no default assignee for the component, I doubt you'll have any success with this issue. However, you could try emailing to ask about the status of the plugin, see email address in user profile linked above. before I start to write a new cmake-plugin from scratch. Maybe you could take over maintainership of the plugin rather than do a full rewrite? There are over 1000 known users of the plugin who could benefit from that. 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-25791) User.impersonate throws ClassCastException when using GitHub auth
rsandell commented on JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth Yes, any plugin that wants to do User.impersonate will get this error when using github auth plugin for authentication. I got it when coding on one of my own plugins. 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Martin Weber edited a comment on JENKINS-25807 Is this plugin still maintained? Resolve it as whatever you like. I just tried to get some feedback from the maintainers before I start to write a new cmake-plugin from scratch. Kanstantsin suggested to ask here. 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Martin Weber commented on JENKINS-25807 Is this plugin still maintained? Resolve it as whatever you like. I just tried to get some feedback from the maintainers before I start to write a new cmake-plugin from scratch. 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] [plot-plugin] (JENKINS-25814) NullPointerException in MatrixPlotPublisher
Brian Smith created JENKINS-25814 NullPointerException in MatrixPlotPublisher Issue Type: Bug Assignee: nidaley Components: plot-plugin Created: 27/Nov/14 6:50 PM Description: Recording plot data ERROR: Publisher hudson.plugins.plot.MatrixPlotPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.plot.MatrixPlotPublisher.perform(MatrixPlotPublisher.java:174) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1709) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: jenkins 1.554.2, Plot plugin 1.8, Windows server and nodes. Project: Jenkins Priority: Major Reporter: Brian Smith 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-25755) SPDY is not working on 1.580
Daniel Beck commented on JENKINS-25755 SPDY is not working on 1.580 SPDY requires use of HTTPS (at least according to Wikipedia). So make sure to use something like java -jar jenkins.war --httpsPort=9090 --spdy=true. 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-25791) User.impersonate throws ClassCastException when using GitHub auth
Hugh Saunders commented on JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth My issue could be related to the authorizeproject plugin, as I stopped seeing these stack traces when I disabled that 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] [core] (JENKINS-25755) SPDY is not working on 1.580
Ireneusz Makowski commented on JENKINS-25755 SPDY is not working on 1.580 any help in that or clarification what is happening? 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] [ssh-slaves-plugin] (JENKINS-25813) Slave agents on Unix machines via ssh - Empty logs
clement igonet updated JENKINS-25813 Slave agents on Unix machines via ssh - Empty logs Change By: clement igonet (27/Nov/14 4:01 PM) Description: 1 connection to linux (centos58-64) slave loops does not start, looping forever. Logs are empty.1 connection to windows (win7-32/cygwin) slave loops does not start, looping forever. Logs are empty.1 connection to windows (win7-64/cygwin)slave loops does not start, looping forever. Logs are empty.1 connection to linux (centos58-32) slave is working after removing and creating a new slave config...1 connection to max (Mac OS X) slave is working after removing and creating a new slave config...Issue impossible to fix because of the lack of information (empty log).All the connections worked well before upgrading to Jenkins V 1.591 and SSH Slaves plugin V 1.9. Now, reverting to older versions does not fix the problem. 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] [ssh-slaves-plugin] (JENKINS-25813) Slave agents on Unix machines via ssh - Empty logs
clement igonet updated JENKINS-25813 Slave agents on Unix machines via ssh - Empty logs Change By: clement igonet (27/Nov/14 3:59 PM) Description: 1 connection to linux (centos58-64) slave loops forever. Logs are empty.1 connection to linux windows (win7-32/cygwin) slave loops forever. Logs are empty.1 connection to linux windows (win7-64/cygwin)slave loops forever. Logs are empty. 1 connection to linux (centos58-32) slave is working after removing and creating a new slave config... 1 connection to max (Mac OS X) slave is working after removing and creating a new slave config... Issue impossible to fix because of the lack of information (empty log).All the connections worked well before upgrading to Jenkins V 1.591 and SSH Slaves plugin V 1.9. Now, reverting to older versions does not fix the problem. 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] [ssh-slaves-plugin] (JENKINS-25813) Slave agents on Unix machines via ssh - Empty logs
clement igonet updated JENKINS-25813 Slave agents on Unix machines via ssh - Empty logs Change By: clement igonet (27/Nov/14 3:55 PM) Description: 1 connection to linux (centos58-64) slave loops forever. Logs are empty.1 connection to linux (win7-32/cygwin) slave loops forever. Logs are empty.1 connection to linux (win7-64/cygwin)slave loops forever. Logs are empty.Issue impossible to fix beacause because of the lack of information ( no empty log).All the connections worked well before upgrading to Jenkins V 1.591 and SSH Slaves plugin V 1.9. Now, reverting to older versions does not fix the problem. 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] [ssh-slaves-plugin] (JENKINS-25813) Slave agents on Unix machines via ssh - Empty logs
clement igonet created JENKINS-25813 Slave agents on Unix machines via ssh - Empty logs Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 27/Nov/14 3:54 PM Description: 1 connection to linux (centos58-64) slave loops forever. Logs are empty. 1 connection to linux (win7-32/cygwin) slave loops forever. Logs are empty. 1 connection to linux (win7-64/cygwin)slave loops forever. Logs are empty. Issue impossible to fix beacause of the lack of information (no log). All the connections worked well before upgrading to Jenkins V 1.591 and SSH Slaves plugin V 1.9. Now, reverting to older versions does not fix the problem. Environment: - Master on debian Jessie (jenkins 1.591 - SSH Slaves plugin 1.9) - Slaves on Centos, Mac and Windows/Cygwin Project: Jenkins Priority: Blocker Reporter: clement igonet 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] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Gregory commented on JENKINS-24608 Test result link displays twice on matrix project page I have the same issue with xUnit and I confirm that it is not related to matrix project - Jenkins ver. 1.591 - xUnit ver. 1.92 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-5135) Adopt everywhere
Daniel Beck commented on JENKINS-5135 Adopt everywhere The default (if unspecified) should probably be changed now to default to escaping. Kohsuke recently mentioned something like that. 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] [remoting] (JENKINS-25803) Slave ping timeout ; build hangs
Daniel Beck commented on JENKINS-25803 Slave ping timeout ; build hangs (would be nice if we could see which channel/slave) https://github.com/jenkinsci/jenkins/commit/99b5fc8f387ee611bb0f764a078367e7842a27c1 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-5135) Adopt everywhere
Alex Earl commented on JENKINS-5135 Adopt everywhere Is this still a valid issue? Are there still jelly files without 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] [role-strategy-plugin] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Lars Nielsen commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts Hi, I would very much like to see a REST API for this. We manage thousands of jobs completely via the rest api, clicking is forbidden . The user/roles setup needs to be automated as well. 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-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Bojan Belic commented on JENKINS-20941 Stored git credentials not used when submodule is updated Hey everyone, for all the ones that don't have an answer on how to fix the problem, I'll write a short guide here on what to do to make it work with a standard Mac-user. The problem many here are probably having is caused by the fact that they have created a Jenkins-daemon (by using the Shell) instead of making a full-fledged user in OSX. Following these steps has worked for me: 1. Make a new administrator user using System Preferences > Users & Groups and call him 'jenkins' and give him a password. 2. Install homebrew to install wget & jenkins using these commands in your terminal: ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" brew install wget brew install jenkins 3. Before starting your Jenkins CI-service, create the following dir and symlinks: mkdir -p ~/Library/LaunchAgents ln -sfv /usr/local/opt/jenkins/*.plist ~/Library/LaunchAgents 4. And afterward choose to either start or stop Jenkins with: launchctl load ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist 5. Jenkins will currently only be accessible through 'localhost:8080'. If you want it to be accessible to other people, change this line in ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist: find and edit: -httpListenAddress=127.0.0.1 TO -httpListenAddress=0.0.0.0 Normally Jenkins should work normally now on your systems and after installing the Git SCM functionality, it shouldn't give you any further errors when trying to access your keychain for submodule-authentication. (unless the user/password are wrong and/or not present) Happy building! 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] [jython-plugin] (JENKINS-25812) Jython plugin no longer provides access to Jenkins internals
Lars Nielsen updated JENKINS-25812 Jython plugin no longer provides access to Jenkins internals Change By: Lars Nielsen (27/Nov/14 1:36 PM) Description: In the original jython plugin, the script was running inside the master jvm and it was thus possible to access Hudson internals, like this: import hudson.modelhudson = hudson.model.Hudson.getInstance() In jenkins this still works perfectly when downgrading the plugin to version 1.3, with the minor change below: import jenkins.modelhudson = jenkins.model.Jenkins.getInstance() In version 1.4 the plugin was changed to execute the script in an external jvm, so Jenkins internals can no longer be accessed.I think the only good reason for having a Jython plugin, is to access Jenkins internals. If you can't do that, you might as well use a regular shell step. and start the jython interpreter yourself, which is a lot more flexible than using the plugin.Please provide an option to run the interpreter in the Jenkins master jvm (In my opinion this should be the default). If you want to get fancy, there shold be a check preventing setting the job to run on another node.I know this was a long time on the way, but I have had to use Hudson at work, and this still works in Hudson.Question: Why cant I pin the plugin version? The pin option only shows up for some plugins. 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] [jython-plugin] (JENKINS-25812) Jython plugin no longer provides access to Jenkins internals
Lars Nielsen created JENKINS-25812 Jython plugin no longer provides access to Jenkins internals Issue Type: Bug Assignee: Unassigned Components: jython-plugin Created: 27/Nov/14 1:19 PM Description: In the original jython plugin, the script was running inside the master jvm and it was thus possible to access Hudson internals, like this: import hudson.model hudson = hudson.model.Hudson.getInstance() In jenkins this still works perfectly when downgrading the plugin to version 1.3, with the minor change below: import jenkins.model hudson = jenkins.model.Jenkins.getInstance() In version 1.4 the plugin was changed to execute the script in an external jvm, so Jenkins internals can no longer be accessed. I think the only good reason for having a Jython plugin, is to access Jenkins internals. If you can't do that, you might as well use a regular shell step. and start the jython interpreter yourself, which is a lot more flexible than using the plugin. Please provide an option to run the interpreter in the Jenkins master jvm (In my opinion this should be the default). If you want to get fancy, there shold be a check preventing setting the job to run on another node. I know this was a long time on the way, but I have had to use Hudson at work, and this still works in Hudson. Question: Why cant I pin the plugin version? The pin option only shows up for some plugins. Environment: Jython plugin 1.4 and newer Jenkins 1.5.9.1 Redhat Project: Jenkins Priority: Critical Reporter: Lars Nielsen 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes Create PR to address this issue: https://github.com/jenkinsci/jabber-plugin/pull/13 @Jordan Are you able to create the plugin from the PR and test 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] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
edwin renner commented on JENKINS-24832 Failed maven builds using -T are showing up as Aborted +1 we are suffering from this problem as well. 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] [delivery-pipeline-plugin] (JENKINS-21291) Loading animation for first load of the view
Patrik Boström commented on JENKINS-21291 Loading animation for first load of the view Created a PR: https://github.com/Diabol/delivery-pipeline-plugin/pull/91 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] [delivery-pipeline-plugin] (JENKINS-21291) Loading animation for first load of the view
Patrik Boström started work on JENKINS-21291 Loading animation for first load of the view Change By: Patrik Boström (27/Nov/14 1:05 PM) Status: Open In Progress 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-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Yves Schumann
commented on JENKINS-23273
RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Updating jenkins on our environment took more than a hour because of this behaviour! This is very frustrating because everytime I need to explain the long downtime...
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] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)
Mads Nielsen resolved JENKINS-25544 as Fixed Default repository name (origin) must work with git scm and multi SCMs git (our case 12285) Change By: Mads Nielsen (27/Nov/14 10:53 AM) 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] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Hugh Saunders commented on JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth I have come across a similar issue, using github oauth, this is preventing builds from starting, despite free executors. Nov 27, 2014 10:38:01 AM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.model.Queue$MaintainTask@33c250dd failed java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:542) at org.jenkinsci.plugins.GithubSecurityRealm$2.loadUserByUsername(GithubSecurityRealm.java:494) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:282) at org.jenkinsci.plugins.authorizeproject.strategy.SpecificUsersAuthorizationStrategy.authenticate(SpecificUsersAuthorizationStrategy.java:108) at org.jenkinsci.plugins.authorizeproject.AuthorizeProjectProperty.authenticate(AuthorizeProjectProperty.java:89) at org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.authenticate(ProjectQueueItemAuthenticator.java:73) at hudson.model.Queue$Item.authenticate(Queue.java:1517) at hudson.model.Node.canTake(Node.java:345) at hudson.model.Queue$JobOffer.canTake(Queue.java:269) at hudson.model.Queue.maintain(Queue.java:1041) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2009) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 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:745) 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] [parameterized-trigger-plugin] (JENKINS-25772) SubversionRevisionBuildTriggerConfigTest.testRevisionParameter fails with SSL handshake
ikedam commented on JENKINS-25772 SubversionRevisionBuildTriggerConfigTest.testRevisionParameter fails with SSL handshake https://github.com/jenkinsci/parameterized-trigger-plugin/pull/75 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
miguel Rodrigues edited a comment on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete @Daniel Beck That is a good assumption, given that my use case is various EC2 instances running the jobs in parallel. some jobs take more time than other, and the node where the parent job is running was probably removed when the job that lasts the most ends. EDIT: I changed the job that triggers all the parallel jobs ( the one that gets the join trigger) to my master node, and everything worked fine. So basically the plugin tries to notify an instance that no longer exists hence, the null pointer exception. 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] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Florian Schmaus commented on JENKINS-25676 Disconnect from XMPP after a few minutes HipChat has a similar behavior addressed in JENKINS-25222. Unfortunately it queries the service name for hipchat: https://github.com/jenkinsci/jabber-plugin/commit/cd9eaf5fa28877fc3d2e42339219168ee3f0c0a3#diff-f633f26543fa04f4d2bad3e2c23d6fc3R442 @kutzi I recommend to re-open this issue, changing it's title to "Add support for automated server pings", remove the server specific code added in JENKINS-25222 and add a generic setting for server pings using existing Smack code https://www.igniterealtime.org/builds/smack/docs/latest/javadoc/org/jivesoftware/smackx/ping/PingManager.html I recommend a default ping interval of 5 minutes, but users should be able to enter a longer ping interval (30min, 1h). 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-25811) Log records presented in Jenkins UI are missing the source when EAP6/jbossas 7 is used
Oliver Gondža created JENKINS-25811 Log records presented in Jenkins UI are missing the source when EAP6/jbossas 7 is used Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 27/Nov/14 10:02 AM Description: While this was working in earlier versions (EAP 5.2 / jbossas 5.2) it misbehaves in (EAP 6.1 / jboss-standalone 7.3). Records presented on $JENKINS/log/XXX are missing the class+method name / logger name. Instead unescaped is printed. This seems to have 2 causes: org.jboss.logmanager.ExtLogRecord that replaced java.util.logging.LogRecord in never version uses "" to signal unknown class/method name instead of null. For whatever reason, never version tend to be less successful in identifying the source. Project: Jenkins Priority: Trivial 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] [promoted-builds-plugin] (JENKINS-20596) Support rebuilding jobs using promoted builds parameter
Mads Mohr Christensen updated JENKINS-20596 Support rebuilding jobs using promoted builds parameter Change By: Mads Mohr Christensen (27/Nov/14 9:57 AM) Issue Type: Bug New Feature Assignee: ragesh_nair Mads Mohr Christensen Component/s: promoted-builds-plugin Component/s: rebuild-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] [promoted-builds-plugin] (JENKINS-20596) Support rebuilding jobs using promoted builds parameter
Mads Mohr Christensen resolved JENKINS-20596 as Fixed Support rebuilding jobs using promoted builds parameter PR merged. Pending release. Change By: Mads Mohr Christensen (27/Nov/14 9:58 AM) 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] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working Still present on Jenkins 1.590 with Subversion plugin 2.4.5. 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] [openid-plugin] (JENKINS-25179) Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login
Omer Weissman commented on JENKINS-25179 Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login Happens to us also, jenkins is deployed as standalone. Many of our users were complaining so we had to downgraded to 2.1 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] [artifactdeployer-plugin] (JENKINS-25806) Artifact Deployer plugin 0.32 doing nothing
pedro reis commented on JENKINS-25806 Artifact Deployer plugin 0.32 doing nothing Add up info: I've tried out and inside Flexible publish 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-17290) Category titles in Available Plugins list appear wrong in reverse sort order
Ruoxi Jiang commented on JENKINS-17290 Category titles in Available Plugins list appear wrong in reverse sort order Issues is fixed. Waiting for pull request to be accepted. #1741 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] [pretested-integration-plugin] (JENKINS-25805) Support for maven projects type (our case 12361)
Bue Petersen edited a comment on JENKINS-25805 Support for maven projects type (our case 12361) Hi Thanks for raising the issue Al, and Daniel thanks for the clarification. It was a specific decision to support Freestyle projects to start with, as that was what most of our customers uses. I don't see there should any problems extending it later to support other types of projects, but it require us to do add more testing at least. I have created issues JENKINS-25810 about only showing the post build step for supported job types. So now we can consider this issue as a feature request to support Maven job types in 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] [pretested-integration-plugin] (JENKINS-25810) Only show postbuild step for supported job types (our case 12369)
Bue Petersen updated JENKINS-25810 Only show postbuild step for supported job types (our case 12369) Change By: Bue Petersen (27/Nov/14 8:20 AM) Summary: Only show postbuild step for supported build job types (our case 12369) 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] [pretested-integration-plugin] (JENKINS-25805) Support for maven projects type (our case 12361)
Bue Petersen updated JENKINS-25805 Support for maven projects type (our case 12361) Change By: Bue Petersen (27/Nov/14 8:15 AM) Summary: 'Use pretested integration' doesn't show up Support for maven projects type (our case 12361) 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] [pretested-integration-plugin] (JENKINS-25810) Only show postbuild step for supported build types (our case 12369)
Bue Petersen updated JENKINS-25810 Only show postbuild step for supported build types (our case 12369) Change By: Bue Petersen (27/Nov/14 8:14 AM) Summary: Only show postbuild step for supported build types (our case 12369) 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up for maven projects (our case 12361)
Bue Petersen updated JENKINS-25805 'Use pretested integration' doesn't show up for maven projects (our case 12361) Change By: Bue Petersen (27/Nov/14 8:14 AM) Issue Type: Bug New Feature 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up for maven projects (our case 12361)
Bue Petersen commented on JENKINS-25805 'Use pretested integration' doesn't show up for maven projects (our case 12361) Hi Thanks for raising the issue Al, and Daniel thanks for the clarification. I was a specific decision to support Freestyle projects to start with, as that was what most of our customers uses. I don't see there should any problems extending it later to support other types of projects, but it require us to do add more testing at least. I have created issues JENKINS-25810 about only showing the post build step for supported job types. So now we can consider this issue as a feature request to support Maven job types in 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] [pretested-integration-plugin] (JENKINS-25810) Only show postbuild step for supported build types
Bue Petersen created JENKINS-25810 Only show postbuild step for supported build types Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 27/Nov/14 8:11 AM Description: The Pretested Integration plugin currently only support Freestyle projects, but the postbuild step shows up on all project types. This is confusing, as the rest of the plugin is missing in the job configuration. Problem reported as part of JENKINS-25805 Project: Jenkins Priority: Minor Reporter: Bue Petersen 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] [pretested-integration-plugin] (JENKINS-25805) 'Use pretested integration' doesn't show up for maven projects (our case 12361)
Bue Petersen updated JENKINS-25805 'Use pretested integration' doesn't show up for maven projects (our case 12361) Change By: Bue Petersen (27/Nov/14 8:04 AM) Summary: 'Use pretested integration' doesn't show up for maven projects (our case 12361) 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.
