[JIRA] [core] (JENKINS-18879) Collecting finbugs analysis results randomly fails with exception
Ramin Baradari commented on JENKINS-18879 Collecting finbugs analysis results randomly fails with exception I downgraded our installation to Jenkins ver. 1.521 but the problem still occurred over night. Jenkins SSH Slaves plugin is at 0.27 Static Analysis Utilities is at 1.50 FindBugs Plug-in is at 4.49 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF and IE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF, Safari and IE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18925) broken Slaves statistics Dashboard Portlet, displaying raw makeStaplerProxy() javascript function instead of numbers
Rene Hess commented on JENKINS-18925 broken Slaves statistics Dashboard Portlet, displaying raw makeStaplerProxy() _javascript_ function instead of numbers Same problem here. Build statistics working correctly, though This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18878) Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server
Joel Huttunen updated JENKINS-18878 Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server Change By: Joel Huttunen (26/Jul/13 6:52 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18809) Discard Unreadable Data results in an NPE
Ramin Baradari commented on JENKINS-18809 Discard Unreadable Data results in an NPE Happens in 1.521 too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Björn Pedersen commented on JENKINS-17734 Claim Report view reports Error Status: 500 Are there any news on this 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H reopened JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Sorry for the Reopen - but we don't have any special Jenkins config regarding Commons. Would be very helpful if you could assist here to find the reason for it... Change By: O H (26/Jul/13 8:03 AM) Resolution: WontFix 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/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
sogabe commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) this will be fixed in 1.525. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H edited a comment on JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Sorry for the Reopen - but we don't have any special Jenkins config regarding Commons. Would be very helpful if you could assist here further to find the reason for it... Using now Jenkins 1.524 and the PTC Plugin 1.17. And still the error: bjava.lang.AbstractMethodError at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H edited a comment on JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Sorry for the Reopen - but we don't have any special Jenkins config regarding Commons. Would be very helpful if you could assist here further to find the reason for it... Using now Jenkins 1.524 and the PTC Plugin 1.17. And still the error: bjava.lang.AbstractMethodError at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) I attached also a Screenshot of an example config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H updated JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Change By: O H (26/Jul/13 8:11 AM) Attachment: 26-07-201310-08-51.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18942) Job DSL should support Fingerprint Publisher
wolfs created JENKINS-18942 Job DSL should support Fingerprint Publisher Issue Type: New Feature Assignee: Justin Ryan Components: job-dsl-plugin Created: 26/Jul/13 8:32 AM Description: Fingerprinting (https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint) should be configurable via the job-dsl. Project: Jenkins Priority: Minor Reporter: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18937) Add DSL support for the Timestamper plugin
wolfs updated JENKINS-18937 Add DSL support for the Timestamper plugin Change By: wolfs (26/Jul/13 8:34 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H edited a comment on JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Sorry for the Reopen - but we don't have any special Jenkins config regarding Commons. Would be very helpful if you could assist here further to find the reason for it... Using now Jenkins 1.524 and the PTC Plugin 1.17. And still the error: bjava.lang.AbstractMethodError at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; java.lang.AbstractMethodError: com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) I attached also a Screenshot of an example config. Perhaps it could be a problem with the SSL certificate? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-13632) AbstractMethodError with PTC Integrity Plugin
O H edited a comment on JENKINS-13632 AbstractMethodError with PTC Integrity Plugin Sorry for the Reopen - but we don't have any special Jenkins config regarding Commons. Would be very helpful if you could assist here further to find the reason for it... Using now Jenkins 1.524 and the PTC Plugin 1.17. And still the errors: This one happens after reconfig (e.g. SSL to no SSL): java.lang.AbstractMethodError at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) And this one is the initial one (without reconfig and after Jenkins fresh restart): com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; java.lang.AbstractMethodError: com.mks.connect.UserApplicationSessionImpl$SSLSocketFactory.createSocket(Ljava/lang/String;ILjava/net/InetAddress;ILorg/apache/commons/httpclient/params/HttpConnectionParams;)Ljava/net/Socket; at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) I attached also a Screenshot of an example config. Perhaps it could be a problem with the SSL certificate? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
stephane Buisson commented on JENKINS-17839 1.514 breaks SSH nodes Same problem in 1.524. What is the workaround, we ares stucked with this ? Thanks all This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
stephane Buisson commented on JENKINS-17839 1.514 breaks SSH nodes Ok updated latest version of ssh slave plugin + manage credential plugin seems to work fin 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/groups/opt_out.
[JIRA] [nodeofflinenotification] (JENKINS-18943) Can not configure Node with Node Offline Email Notification plugin
Bakkiaraj Murugesan created JENKINS-18943 Can not configure Node with Node Offline Email Notification plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: nodeofflinenotification Created: 26/Jul/13 9:49 AM Description: Hi, When I try to add Node Offline Email Notification to existing node, (Please see screen shot) and press save, I get following exception in Jenkins web interface. --- Stack trace javax.servlet.ServletException: java.lang.AssertionError: class org.jruby.proxy.hudson.slaves.NodeProperty$Proxy3 is missing its descriptor at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:201) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 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.plugins.collabnet.auth.CNFilter.doFilter(CNFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:118) 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:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [core] (JENKINS-18944) UndeclaredThrowableException while recording fingerprints
Ramin Baradari created JENKINS-18944 UndeclaredThrowableException while recording fingerprints Issue Type: Bug Assignee: Unassigned Components: core, master-slave Created: 26/Jul/13 10:08 AM Description: The following exception was thrown during fingerprint recording. ERROR: Publisher hudson.tasks.Fingerprinter aborted due to exception java.lang.reflect.UndeclaredThrowableException at $Proxy6.fetch3(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:156) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2442) at java.lang.Class.getDeclaredMethod(Class.java:1952) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1411) at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:69) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:481) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:455) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.init(ObjectStreamClass.java:455) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:352) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1130) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at java.util.ArrayList.writeObject(ArrayList.java:710) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:975) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.perform(UserRequest.java:126) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:165) ... 36 more Environment: Jenkins ver. 1.521, Master Slave on Linux Project: Jenkins Priority: Major Reporter: Ramin Baradari 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
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Greg Nion commented on JENKINS-18930 Missing TestResultColumn() constructor Hi Fred, thanks for your prompt response. I'll test it as soon as I setup a dev instance of my Jenkins Cheers, Greg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodeofflinenotification] (JENKINS-18943) Can not configure Node with Node Offline Email Notification plugin
Bakkiaraj Murugesan updated JENKINS-18943 Can not configure Node with Node Offline Email Notification plugin Screen Shot of Node configuration page Change By: Bakkiaraj Murugesan (26/Jul/13 10:20 AM) Attachment: 11.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ant] (JENKINS-14534) After jenkins upgrade from 1.464 to 1.474, while executing a job..its recreating the Ant/Maven installation tools again.
evernat commented on JENKINS-14534 After jenkins upgrade from 1.464 to 1.474, while executing a job..its recreating the Ant/Maven installation tools again. Is it still an 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18945) Absolute path in multijob build page resulting error when jenkins isn't in root folder off app server
Piotr Kral created JENKINS-18945 Absolute path in multijob build page resulting error when jenkins isnt in root folder off app server Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 26/Jul/13 11:54 AM Description: My Jenkins server is hosted on: https://servername/jenkins And when I run a Multijob job and click a build i see a page with summary information: No changes from last build. Started by user My user Phaze_name Job_name build#304 ( 19 min and counting ) The "build#304" is a link to build info about 304 build off Job_name At least it should be. The link is probably absolute and in result it's missing prefix "jenkins": instead off: https://servername/jenkins/job/Job_name/304/ it is: https://servername/job/Job_name/304/ Due Date: 26/Jul/13 12:00 AM Environment: Jenkins is deployed on Centos 6 + Tomcat6 + Apache Project: Jenkins Labels: plugin multi-job Priority: Major Reporter: Piotr Kral This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
sogabe commented on JENKINS-18929 OutOfMemoryError: PermGen space use -XX:MaxPermSize option This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
David Ishee commented on JENKINS-18929 OutOfMemoryError: PermGen space I set MaxPermSize to 256M. We'll see if that helps. If it is a memory leak, it will just postpone the crash. I'll use jmap next time to get a heap dump too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
David Ishee edited a comment on JENKINS-18929 OutOfMemoryError: PermGen space I set MaxPermSize to 256M. We'll see if that helps. If it is a memory leak, it will just postpone the crash. I'll use jmap next time to get a heap dump too. This is how things are running right now after about 24 hrs of uptime: jmap -heap 32633 Attaching to process ID 32633, please wait... Debugger attached successfully. Server compiler detected. JVM version is 14.3-b01 using thread-local object allocation. Parallel GC with 4 thread(s) Heap Configuration: MinHeapFreeRatio = 40 MaxHeapFreeRatio = 70 MaxHeapSize = 1572864000 (1500.0MB) NewSize = 2686976 (2.5625MB) MaxNewSize = 17592186044415 MB OldSize = 5439488 (5.1875MB) NewRatio = 2 SurvivorRatio= 8 PermSize = 21757952 (20.75MB) MaxPermSize = 268435456 (256.0MB) Heap Usage: PS Young Generation Eden Space: capacity = 212008960 (202.1875MB) used = 41851216 (39.91242980957031MB) free = 170157744 (162.2750701904297MB) 19.74030531539799% used >From Space: capacity = 11534336 (11.0MB) used = 11534336 (11.0MB) free = 0 (0.0MB) 100.0% used To Space: capacity = 27394048 (26.125MB) used = 0 (0.0MB) free = 27394048 (26.125MB) 0.0% used PS Old Generation capacity = 93519872 (89.1875MB) used = 65702256 (62.65855407714844MB) free = 27817616 (26.528945922851562MB) 70.25486091341101% used PS Perm Generation capacity = 128450560 (122.5MB) used = 87743104 (83.6783447265625MB) free = 40707456 (38.8216552734375MB) 68.30885283801021% used Will attach output of jmap -histo and jmap -permstat (larger output) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
David Ishee updated JENKINS-18929 OutOfMemoryError: PermGen space Change By: David Ishee (26/Jul/13 12:31 PM) Attachment: permstat.txt Attachment: histo.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ftppublisher] (JENKINS-18946) FTP Publisher can't read file
Thorsten Liepert created JENKINS-18946 FTP Publisher cant read file Issue Type: Bug Affects Versions: current Assignee: benjaminjaton Components: ftppublisher, publish-over-ftp Created: 26/Jul/13 1:14 PM Description: The FTP Publisher always sets a build to Unstable because it can't read the file. Jenkins has all rights to write and read the files from ftp. file:/var/lib/jenkins/jobs/ConnectivityGateway_WeeklyBuilds/workspace/ current root dir /upload/jenkins current root dir /upload/jenkins/cgw/weekly ERROR: Failed to upload files java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:146) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.FilterInputStream.read(FilterInputStream.java:83) at java.io.PushbackInputStream.read(PushbackInputStream.java:139) at org.apache.commons.net.io.FromNetASCIIInputStream.__read(FromNetASCIIInputStream.java:75) at org.apache.commons.net.io.FromNetASCIIInputStream.read(FromNetASCIIInputStream.java:170) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at org.apache.commons.net.telnet.TelnetInputStream.__read(TelnetInputStream.java:114) at org.apache.commons.net.telnet.TelnetInputStream.run(TelnetInputStream.java:535) at java.lang.Thread.run(Thread.java:679) Build step 'Publish artifacts to FTP' changed build result to UNSTABLE Project: Jenkins Priority: Major Reporter: Thorsten Liepert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [instant-messaging] (JENKINS-18947) Unable to use environment variables within the list of notification targets in the jabber plugin
Martin Peticek
created JENKINS-18947
Unable to use environment variables within the list of notification targets in the jabber plugin
Issue Type:
Improvement
Affects Versions:
current
Assignee:
kutzi
Components:
instant-messaging, jabber
Created:
26/Jul/13 1:33 PM
Description:
I tried to set up a Jabber notification that will be sent to $BUILD_USER_ID (environment variable that is set by another plugin), so the user who started the build will be notified when it is done. However the environment variables in the list of notification recipients does not resolve environment variables, so it tried to sent to user named literally "$BUILD_USER_ID" on the jabber server (not the intended recipient...)
It would be nice if environment variables would be resolved in the list of people to notify, to enable notification to recipient addresses calculated by some other plugin.
Following quick hack does what I need to do, but it is not a clean solution, and because of the storage format (plugin stores notification targets internally not as a string from configuration, but as a list of validated jabber IDs) it will be hard to change this cleanly and correctly - since environment variable may or may not contain complete username and may or may not contain more space separated targets, it would probably be necessary to store the target settings as a literal string, converting it to resolved list at end of the build once all the env vars are known and available (and not at time when configuration is saved).
--- src/main/java/hudson/plugins/im/IMPublisher.java ---
index 6fb5065..2a49a63 100644
@@ -582,6 +582,9 @@ public abstract class IMPublisher extends Notifier implements BuildStep, MatrixA
{
try {
log(buildListener, "Sending notification to: " + target.toString());
+target = getIMDescriptor().getIMMessageTargetConverter().fromString(
+build.getEnvironment(buildListener).expand(target.toString()));
+log(buildListener, "(expanded) Sending notification to: " + target.toString());
sendNotification(msg, target, buildListener);
} catch (final Throwable t) {
log(buildListener, "There was an error sending notification to: " + target.toString() + "\n" + ExceptionHelper.dump(t));
Project:
Jenkins
Priority:
Major
Reporter:
Martin Peticek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18845) Jenkins 1.522 - Repository Browser Sventon is gone
Tom Sch updated JENKINS-18845 Jenkins 1.522 - Repository Browser Sventon is gone Change By: Tom Sch (26/Jul/13 1:45 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-18948) Unable to claim builds using the build-flow plugin
Aidan McGinley created JENKINS-18948 Unable to claim builds using the build-flow plugin Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow, claim Created: 26/Jul/13 2:03 PM Description: When a job configured using the build-flow plugin fails it is not possible to claim it. When you click the claim button a HTTP post is submitted with the following data: reason=sticky=onSubmit=Claim Claiming a regular job results in something like this in the HTTP request reason=sticky=onjson=%7B%22reason%22%3A+%22%22%2C+%22sticky%22%3A+true%7DSubmit=Claim Because of the malformed data in the submission you get an Error 400 with the message "Exception: This page expects a form submission" Environment: Jenkins 1.524 build-flow 0.9 claim 2.2 Project: Jenkins Labels: claim build-flow Priority: Major Reporter: Aidan McGinley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18949) Renaming Project causes content encoding error
Dennis McCurdy created JENKINS-18949 Renaming Project causes content encoding error Issue Type: Bug Affects Versions: current Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 26/Jul/13 2:22 PM Description: When renaming a job in Jenkins 1.524 you do not get the yes/no dialog when you press the Apply button, but you get an error and a NPE. Environment: Ubuntu Fix Versions: current Project: Jenkins Labels: jenkins Priority: Major Reporter: Dennis McCurdy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Greg Nion commented on JENKINS-18930 Missing TestResultColumn() constructor tested successfully! Waiting for your delivery. Thanks a lot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Greg Nion assigned JENKINS-18930 to Fred G Missing TestResultColumn() constructor Change By: Greg Nion (26/Jul/13 2:35 PM) Assignee: GregNion FredG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller created JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Issue Type: Bug Assignee: Marco Miller Components: valgrind Created: 26/Jul/13 2:54 PM Description: valgrind-plugin makes jenkins run out of memory under heavy use. This is caused by too many (all) Report objects being retained in heap by Result objects. Fix is about making such report objects on-demand or just-in-time, rather than always and too early (and as kept forever or so). We at Ericsson have production (jenkins) instances that were recently hit by this bug, in terms of JVMs running out-of-memory. We indeed clearly saw such many large report objects retaining the most of our heap as per profiling of the latter. Project: Jenkins Priority: Major Reporter: Marco Miller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-18951) Problems with too long paths
O H created JENKINS-18951 Problems with too long paths Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 26/Jul/13 3:09 PM Description: Last Built Revision: Revision 2f3e4adfdbf5f19ae77421546c2b575ac41f6304 (origin/master) Fetching changes from 1 remote Git repository Fetching upstream changes from https://xx:x...@fisheye...net/git/.git Commencing build of Revision d5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7 (origin/master) Checking out Revision d5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7 (origin/master) FATAL: Could not checkout null with start point d5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7 hudson.plugins.git.GitException: Could not checkout null with start point d5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7 at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:931) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1285) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1269) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.plugins.git.GitException: Command "c:\git\bin\git.exe checkout -f d5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7" returned status code 1: stdout: stderr: error: unable to create file 5000_Construction/5100_Code_Base/Tools/JPA2Generation/com.x..xtext.persistencemodel.datascript.ui/src-gen/com//tss/xtext/persistencemodel/ui/contentassist/antlr/PartialDatascriptContentAssistParser.java (No such file or directory) Environment: Windows Server, latest Jenkins version Project: Jenkins Priority: Major Reporter: O H This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-18951) Problems with too long paths
O H updated JENKINS-18951 Problems with too long paths Change By: O H (26/Jul/13 3:10 PM) Description: Thereseemstobeaproblemwithpathnamesthatarelongerthancertainthreshold(180chars?): LastBuiltRevision:Revision2f3e4adfdbf5f19ae77421546c2b575ac41f6304(origin/master)Fetchingchangesfrom1remoteGitrepositoryFetchingupstreamchangesfromhttps://xx:x...@fisheye...net/git/.gitCommencingbuildofRevisiond5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7(origin/master)CheckingoutRevisiond5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7(origin/master)FATAL:Couldnotcheckoutnullwithstartpointd5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7hudson.plugins.git.GitException:Couldnotcheckoutnullwithstartpointd5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7athudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:931)athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1285)athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269)athudson.FilePath.act(FilePath.java:852)athudson.FilePath.act(FilePath.java:825)athudson.plugins.git.GitSCM.checkout(GitSCM.java:1269)athudson.model.AbstractProject.checkout(AbstractProject.java:1325)athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)athudson.model.Run.execute(Run.java:1516)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)athudson.model.ResourceController.execute(ResourceController.java:88)athudson.model.Executor.run(Executor.java:236)Causedby:hudson.plugins.git.GitException:Commandc:\git\bin\git.execheckout-fd5cba9a47c5a51b5e6ba3f3ff9a94849f63b87d7returnedstatuscode1:stdout:stderr:error:unabletocreatefile5000_Construction/5100_Code_Base/Tools/JPA2Generation/com.x..xtext.persistencemodel.datascript.ui/src-gen/com//tss/xtext/persistencemodel/ui/contentassist/antlr/PartialDatascriptContentAssistParser.java(Nosuchfileordirectory) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller started work on JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Change By: Marco Miller (26/Jul/13 3:29 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/groups/opt_out.
[JIRA] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller commented on JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Fix pull-requested = https://github.com/jenkinsci/valgrind-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [project-stats] (JENKINS-18952) Option to change Last Successful Artifacts for a project to Latest Artifacts
Steve Carter created JENKINS-18952 Option to change Last Successful Artifacts for a project to Latest Artifacts Issue Type: Improvement Assignee: Unassigned Components: project-stats Created: 26/Jul/13 3:57 PM Description: I have a set of test-run jobs that each end up with an HTML report of the test results. Our suite reports a status code according to whether the test run was clean. We want the job to fail if the suite fails (easy, and working fine) But was also want the report to wind up in the job's homepage, where right now we have "Latest Successful Artifacts". This could be done as an option in the job config to choose "Archive Last Artifacts even on failure" or something. Project: Jenkins Labels: artifact archive failed options Priority: Major Reporter: Steve Carter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clover] (JENKINS-18953) Clover java.lang.IndexOutOfBoundsException
Greg Baysden created JENKINS-18953 Clover java.lang.IndexOutOfBoundsException Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: clover Created: 26/Jul/13 4:01 PM Description: Running Jenkins 1.505 on CentOS 6.2 Linux x86_64 under apache-tomcat-7.0.29. Clover plug-in version 4.0.6. I have the CLOVER license string set in the global Jenkins config. My build job is free-style, and I have an build step "invoke Ant" using Ant 1.8.4.I have Clover enabled in the Build Environment section checked as follows: [ * ] Automatically record and report Code Coverage using Clover. Currently for Ant builds only. Generate an historical report [ * ] Generate a json report [ * ] I get this error when I run the build job after SCM update and before the Ant build step: ... FATAL: Index: 2, Size: 2 java.lang.IndexOutOfBoundsException: Index: 2, Size: 2 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at hudson.plugins.clover.CloverBuildWrapper$CloverDecoratingLauncher.decorateArgs(CloverBuildWrapper.java:188) at hudson.plugins.clover.CloverBuildWrapper$CloverDecoratingLauncher.launch(CloverBuildWrapper.java:163) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Thanks for advice/help on this. -Greg Environment: Linux Project: Jenkins Priority: Minor Reporter: Greg Baysden This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [project-stats] (JENKINS-18952) Option to change Last Successful Artifacts for a project to Latest Artifacts
kutzi commented on JENKINS-18952 Option to change Last Successful Artifacts for a project to Latest Artifacts Seems not to be related to project statistics plugin, but to Jenkins 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-18954) add console log line for reason that the build is marked as unstable when thresholds are exceeded
teilo created JENKINS-18954 add console log line for reason that the build is marked as unstable when thresholds are exceeded Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core, checkstyle, findbugs, pmd, warnings Created: 26/Jul/13 4:38 PM Description: If the anaysis plugin has a threshold that is set to mark the build as unstable no entry is put in the build console log to show why the build is marked as unstable. This causes some confusion to users, but also means it is not simple to integrate with the "Build Failure Analyser" so that the reason for the unstable project is immediately obvious. It would be nice if the there was a line "plugin Build has more failures that the threshold amount - marking unstable." Project: Jenkins Priority: Major Reporter: teilo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-18954) add console log line for reason that the build is marked as unstable when thresholds are exceeded
teilo commented on JENKINS-18954 add console log line for reason that the build is marked as unstable when thresholds are exceeded (obvserved behaviour with Maven2 project type - freesyle may exhibit different behaviour) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-18954) add console log line for reason that the build is marked as unstable when thresholds are exceeded
teilo updated JENKINS-18954 add console log line for reason that the build is marked as unstable when thresholds are exceeded Change By: teilo (26/Jul/13 4:39 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-18955) Add multiple scm support to Bazaar plugin
Maxime Chambreuil created JENKINS-18955 Add multiple scm support to Bazaar plugin Issue Type: New Feature Affects Versions: current Assignee: Monty Taylor Components: bazaar Created: 26/Jul/13 4:45 PM Description: The current Bazaar plugin does not provide a way to specify a subdirectory that could be used to "bzr branch" a URL in a multiple SCM job. Due Date: 31/Aug/13 12:00 AM Project: Jenkins Priority: Major Reporter: Maxime Chambreuil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-18955) Add multiple scm support to Bazaar plugin
Maxime Chambreuil commented on JENKINS-18955 Add multiple scm support to Bazaar plugin Currently there is a casting issue and the Bazaar plugin cleanup the home directory of the job, deleting the previous SCMs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Dave Kichler assigned JENKINS-18361 to Dave Kichler Provide build report API support Change By: Dave Kichler (26/Jul/13 4:47 PM) Assignee: DaveKichler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Dave Kichler started work on JENKINS-18361 Provide build report API support Change By: Dave Kichler (26/Jul/13 4:47 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Dave Kichler commented on JENKINS-18361 Provide build report API support Investigating how to expose additional sub-build info through the API, possibly even through injected environment variables 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/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
Jesse Glick commented on JENKINS-8856 StreamCorruptedException One user reported that the stream corruption was in fact the text Killed, and that /var/log/messages mentioned kernel: java invoked oom-killer, i.e. the slave OS (Linux) had run out of memory and was killing off slave agents. Unfortunately this message seems to have been dumped into the remoting channel and thus confused the master (which saw the K and died). The SSH Slaves plugin is supposed to disconnect the original stdio streams from the channel once the connection is set up, but perhaps this is not working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-17548) FxCop results not being displayed for non-source files
Ryan Davis commented on JENKINS-17548 FxCop results not being displayed for non-source files I forked the code and got the violations being displayed. I looked into changing FxCopParser.parseIssue, but that's a rabbit-hole for another day. Code: https://github.com/AccelerationNet/violations-plugin/tree/JENKINS-17548 Pull request: https://github.com/jenkinsci/violations-plugin/pull/33 Binary you can upload to jenkins: https://github.com/AccelerationNet/violations-plugin/releases/tag/violations-0.7.15+JENKINS-17548 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
SCM/JIRA link daemon commented on JENKINS-8856 StreamCorruptedException Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/remoting/HexDump.java src/test/java/hudson/remoting/HexDumpTest.java http://jenkins-ci.org/commit/remoting/d0334ba25b503038e17488cdbd5dd9bb5cb8121c Log: JENKINS-8856 Diagnostic improvement: show ‘'i' 'l' 'l' 'e' 'd' 0x0a’ rather than ‘696c6c65640a’, so it is more obviously the rest of ‘Killed’. Compare: https://github.com/jenkinsci/remoting/compare/09524af34b57...d0334ba25b50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick resolved JENKINS-10234 as Duplicate Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (26/Jul/13 5:51 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/groups/opt_out.
[JIRA] [core] (JENKINS-9913) Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent
Jesse Glick updated JENKINS-9913 Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent Not a bug per se, but Jenkins needs to make sure that post-build actions which require the previous build to be complete (a) are documented to do so, e.g. in inline help; (b) print a helpful message to the build log when waiting for a previous build. And of course wherever feasible, offer an option to not block in this way, or to perform the processing dependent on the previous build asynchronously, e.g. in a RunListener. Change By: Jesse Glick (26/Jul/13 5:55 PM) Summary: Concurrentbuildsgettingbatched/nodesnotgettingreleased Notobviouswhysomepost-buildtasksenforceserialbehavioreven when jobs builds are completed concurrent Labels: concurrent-buildjunit Assignee: KohsukeKawaguchi JesseGlick Priority: Blocker Major Component/s: core Component/s: concurrent-build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Jesse Glick commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I think the default needs to be changed to use the slave FS root. We should default to a safe and expected configuration; in the rare case that someone runs multiple slaves on one machine, if they find the duplicated caches to consume too much space, they can decide to share them in a location of their choice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Kohsuke Kawaguchi resolved JENKINS-18578 as Fixed Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable The -jar-cache option in slave.jar lets you set the location of the cache since remoting 2.24. Change By: Kohsuke Kawaguchi (26/Jul/13 6:39 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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/groups/opt_out.
[JIRA] [core] (JENKINS-18956) Cache location should be configurable through the GUI
cowwoc created JENKINS-18956 Cache location should be configurable through the GUI Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 26/Jul/13 6:50 PM Description: This is a follow-up to JENKINS-18578. The cache location should be configurable through the GUI. "Launch slave agents on Unix machines via SSH" does not allow specifying -jar-cache so we are expected to manually edit the machine configuration by hand, making it a maintenance nightmare. If this configuration were configurable by GUI, we could create a Slave "template" and copy it when creating new nodes. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
cowwoc commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I disagree with the way this was resolved, so I filed JENKINS-18956. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18459) IOException: No Such File
SCM/JIRA link daemon commented on JENKINS-18459 IOException: No Such File Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/FileSystemJarCache.java http://jenkins-ci.org/commit/remoting/8c85a77a733473820c1815d9cdf5a30feddd6cbb Log: JENKINS-18459 reporting where it's failing to write to assist diagnostics This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18549) No timeout on polling threads
SCM/JIRA link daemon commented on JENKINS-18549 No timeout on polling threads Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/RemoteClassLoader.java http://jenkins-ci.org/commit/remoting/cca2fa6db9dd92e03b4a2982379c3ab078196875 Log: FIXED JENKINS-18549 Failed to cache a jar file shouldn't fail a classloading. Compare: https://github.com/jenkinsci/remoting/compare/d0334ba25b50...cca2fa6db9dd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Jesse Glick reopened JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Did you miss my comment? IMHO the default should be to use the slave FS root. Change By: Jesse Glick (26/Jul/13 6:59 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite created JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Jul/13 7:14 PM Description: Steps I used to see the issue: installed Git Client plugin 1.1.1 and restarted Jenkins downloaded and installed Git Plugin 2.0 beta and restarted Jenkins executed several successful builds without changing configurations confirmed those builds were correctly responding to build hooks use configuration page to delete git as executable, add jgit submitted another change to git repository, watched hooks activate No build from Jenkins, and a null pointer exception is in the log file. SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@21d1ff77p4-port-linux-Merge java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:34) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1105) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:299) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:724) Environment: 64 bit Debian Linux testing running Jenkins 1.509.2 in winstone container running on Oracle JDK 7 Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite 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
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta If I click the "Build Now" button on that job, it reports the null pointer exception: Started by user anonymous Building remotely on fc-nagios-a in workspace /var/lib/jenkins/mwaite6-slave/workspace/p4-port-linux-Merge selected Git installation does not exists. Using Default Fetching changes from the remote Git repository FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:34) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1105) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:299) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:724) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta When I select "Build Now" on another job, it includes the message in its output: selected Git installation does not exists. Using Default That surprises me, since the "JGit" implementation is the only available implementation on my Jenkins server currently, and it is built into 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/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta If I then define a Git command line provider in the global configurations and adjust the problem job to use that command line provider, the job works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18361) Provide build report API support
Dave Kichler commented on JENKINS-18361 Provide build report API support Created pull request for review and acceptance: https://github.com/jenkinsci/tikal-multijob-plugin/pull/25 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-16316) global variable not updated
Jesse Glick updated JENKINS-16316 global variable not updated Change By: Jesse Glick (26/Jul/13 7:53 PM) URL: https://github.com/jenkinsci/envinject-plugin/pull/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Luiz Papa commented on JENKINS-17734 Claim Report view reports Error Status: 500 If you add a file named sidepanel.jelly with any content (e.g. divCaims report/div) on the folder src/main/resources/hudson/plugins/claim/ClaimedBuildsReport and rebuild the error stop happening. But I am not sure I undertood the expected behaviour because no builds are shown in the report, not even the broken builds... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
SCM/JIRA link daemon commented on JENKINS-17960 Indicate if tests dont go to plan Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly http://jenkins-ci.org/commit/tap-plugin/2127053964d7d4b0b8a3038658ef231a0a214e31 Log: FIXED JENKINS-17960 FIXED JENKINS-17781 Adding option to validate number of planned tests and number of tests executed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
SCM/JIRA link daemon commented on JENKINS-17781 TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly http://jenkins-ci.org/commit/tap-plugin/2127053964d7d4b0b8a3038658ef231a0a214e31 Log: FIXED JENKINS-17960 FIXED JENKINS-17781 Adding option to validate number of planned tests and number of tests executed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
SCM/JIRA link daemon commented on JENKINS-17781 TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Code changed in jenkins User: Bruno P. Kinoshita Path: src/test/java/org/tap4j/plugin/issue16647/TestIssue16647.java src/test/java/org/tap4j/plugin/issue16964/TestIssue16964.java http://jenkins-ci.org/commit/tap-plugin/c52f18350d32a93e5242e872eb8c24f756544b7d Log: JENKINS-17960 JENKINS-17781 Fixing tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
SCM/JIRA link daemon commented on JENKINS-17960 Indicate if tests dont go to plan Code changed in jenkins User: Bruno P. Kinoshita Path: src/test/java/org/tap4j/plugin/issue16647/TestIssue16647.java src/test/java/org/tap4j/plugin/issue16964/TestIssue16964.java http://jenkins-ci.org/commit/tap-plugin/c52f18350d32a93e5242e872eb8c24f756544b7d Log: JENKINS-17960 JENKINS-17781 Fixing tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
Bruno P. Kinoshita resolved JENKINS-17960 as Fixed Indicate if tests dont go to plan Change By: Bruno P. Kinoshita (26/Jul/13 8:25 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/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
Bruno P. Kinoshita resolved JENKINS-17781 as Fixed TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Change By: Bruno P. Kinoshita (26/Jul/13 8:25 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-16316) global variable not updated
Jesse Glick updated JENKINS-16316 global variable not updated I filed a new pull request to fix this. Upgrading priority since this bug breaks basic Jenkins functionality merely by installing a plugin, so it is far from obvious to a user where to start diagnosis. Change By: Jesse Glick (26/Jul/13 8:24 PM) Priority: Major Critical URL: https://github.com/jenkinsci/envinject-plugin/pull/ 14 20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18719) Also show job name in list view configuration
Daniel Beck commented on JENKINS-18719 Also show job name in list view configuration https://github.com/jenkinsci/jenkins/pull/883 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18549) No timeout on polling threads
Rob Petti commented on JENKINS-18549 No timeout on polling threads Kohsuke's change doesn't seem to relate to this ticket, so please disregard. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18719) Also show job name in list view configuration
Daniel Beck assigned JENKINS-18719 to Daniel Beck Also show job name in list view configuration Change By: Daniel Beck (26/Jul/13 8:34 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-18958) Expose full name of parent job as an environment variable
Jonathan Zimmerman created JENKINS-18958 Expose full name of parent job as an environment variable Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 26/Jul/13 8:44 PM Description: In an environment using folders the PROMOTED_JOB_NAME cannot be relied upon to differentiate two different jobs. Ideally the full name of the build being promoted would be exposed as PROMOTED_JOB_FULL_NAME. The quick and dirty is rather simple: when building the environment variables set PROMOTION_JOB_FULL_NAME to target.getParent().getFullName(). Project: Jenkins Priority: Major Reporter: Jonathan Zimmerman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Bruno P. Kinoshita commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Hi all, chiming in. The issue is due to a validation error. From what I understood, the plug-in uses DTKit framework and a set of XSD's (and maybe other validation schemas) to validate the input files. In the case of the nosetests.xml file, I used the plug-in version from GitHub, branch master. Debugging the plug-in looks like it uses junit-7.xsd 1 from DTKit. If you are curious, copy the contents of nosetests.xml attached to this issue, and the junit-7.xsd contents, and paste them at http://www.utilities-online.info/xsdvalidation The following error message is displayed: Not valid. Error - Line 1, 110: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 110; cvc-complex-type.3.2.2: Attribute 'skip' is not allowed to appear in element 'testsuite'. I'll take a look at the DTKit to see if it's possible to send a pull request to its repository. Cheers /Bruno 1 https://svn.jenkins-ci.org/trunk/hudson/dtkit/dtkit-format/dtkit-junit-model/src/main/resources/com/thalesgroup/dtkit/junit/model/xsd/junit-7.xsd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Marc Seeger commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds How is this supposed to be a feature? A testrun that doesn't have anything to do with another testrun being blocked? This just got closed as a duplicate. Is this in relation to JENKINS-9913? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Marc Seeger edited a comment on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds How is this supposed to be a feature? A testrun that doesn't have anything to do with another testrun being blocked? This isn't even for parallel runs, this is for completely unrelated jobs. This just got closed as a duplicate. Is this in relation to JENKINS-9913? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18959) /log/all polluted with FINE* messages from other loggers
Jesse Glick created JENKINS-18959 /log/all polluted with FINE* messages from other loggers Issue Type: Bug Assignee: Jesse Glick Components: core Created: 26/Jul/13 9:11 PM Description: If you define a custom logger that captures messages at FINE or below, they also appear in /log/all, which is confusing and clouds the main log display. Project: Jenkins Labels: logging Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18959) /log/all polluted with FINE* messages from other loggers
SCM/JIRA link daemon commented on JENKINS-18959 /log/all polluted with FINE* messages from other loggers Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/WebAppMain.java http://jenkins-ci.org/commit/jenkins/010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258 Log: FIXED JENKINS-18959 /log/all should not show FINE messages from custom loggers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18959) /log/all polluted with FINE* messages from other loggers
SCM/JIRA link daemon resolved JENKINS-18959 as Fixed /log/all polluted with FINE* messages from other loggers Change By: SCM/JIRA link daemon (26/Jul/13 9:23 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/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite created JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Jul/13 9:52 PM Description: My 2.5 GB git repository cloned to this computer (from another local area network computer using git protocol) in about 6.5 minutes using the Git plugin 2.0 beta with the Git command line provider. The same git repository cloning from the same server to the same Jenkins machine using the jgit provider (instead of the Git CLI) still has not finished after 14 minutes. There are indications on other jobs that the first time clone of that large repository may never complete. Environment: Debian x86 testing with Oracle JDK 7 Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Jon Blake commented on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel I tried to upgrade from 1.519 to 1.522 and 1.5.24 and got these same errors. Our system uses linux slaves and this is blocking us from upgrading. Hoping this regression will get fixed in an upcoming release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18940) {wl.source} command line override token doesn't get replaced
Raphael CHAUMIER
started work on JENKINS-18940
{wl.source} command line override token doesnt get replaced
Change By:
Raphael CHAUMIER
(26/Jul/13 10:03 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18940) {wl.source} command line override token doesn't get replaced
Raphael CHAUMIER
commented on JENKINS-18940
{wl.source} command line override token doesnt get replaced
Thanks for your report.
It will be fixed in the 2.5 version. I'm releasing 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18882) Add icon with transparency
Raphael CHAUMIER resolved JENKINS-18882 as Fixed Add icon with transparency Change By: Raphael CHAUMIER (26/Jul/13 10:19 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18882) Add icon with transparency
Raphael CHAUMIER closed JENKINS-18882 as Fixed Add icon with transparency Change By: Raphael CHAUMIER (26/Jul/13 10:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18940) {wl.source} command line override token doesn't get replaced
Raphael CHAUMIER
resolved JENKINS-18940 as Fixed
{wl.source} command line override token doesnt get replaced
Change By:
Raphael CHAUMIER
(26/Jul/13 10:19 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18883) Value of cron 'Deploy Periodically' not visible
Raphael CHAUMIER closed JENKINS-18883 as Fixed Value of cron Deploy Periodically not visible Change By: Raphael CHAUMIER (26/Jul/13 10:21 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18959) /log/all polluted with FINE* messages from other loggers
dogfood commented on JENKINS-18959 /log/all polluted with FINE* messages from other loggers Integrated in jenkins_main_trunk #2751 FIXED JENKINS-18959 /log/all should not show FINE messages from custom loggers. (Revision 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258) Result = SUCCESS Jesse Glick : 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258 Files : changelog.html core/src/main/java/hudson/WebAppMain.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
Bruno P. Kinoshita closed JENKINS-17960 as Fixed Indicate if tests dont go to plan Fixed in 1.13 Change By: Bruno P. Kinoshita (27/Jul/13 1:55 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
Bruno P. Kinoshita closed JENKINS-17781 as Fixed TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Fixed in 1.13 Change By: Bruno P. Kinoshita (27/Jul/13 1:57 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18813) AbstractProject.removeTrigger raises UnsupportedOperationException
SCM/JIRA link daemon commented on JENKINS-18813 AbstractProject.removeTrigger raises UnsupportedOperationException Code changed in jenkins User: mcdonan Path: core/src/main/java/hudson/model/AbstractProject.java test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/edf932be37ffdad965c3fcaf6c7d7a6f1efc54f8 Log: FIXED JENKINS-18813 Add/RemoveTrigger now works Ensure the addTrigger and removeTrigger methods only use methods that are supported by DescribableList. This means no indexed operations are supported, so use only Iterator#remove and Collection#add Add Integration Tests to ensure methods work as expected This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18813) AbstractProject.removeTrigger raises UnsupportedOperationException
SCM/JIRA link daemon resolved JENKINS-18813 as Fixed AbstractProject.removeTrigger raises UnsupportedOperationException Change By: SCM/JIRA link daemon (27/Jul/13 4:09 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/groups/opt_out.
