[JIRA] [jenkins-jira-issue-updater] (JENKINS-18835) Exception after upgrade to version 1.514 from 1.488
Kunal Chaturvedi created JENKINS-18835 Exception after upgrade to version 1.514 from 1.488 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-jira-issue-updater Created: 19/Jul/13 6:12 AM Description: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/proj/jkadm100/apache-tomcat-6.0.35/webapps/jenkins/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/proj/jkadm100/apache-tomcat-6.0.35/webapps/jenkins/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:736) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) 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 org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] [scm-sync-configuration] (JENKINS-13593) Seems to not handle having builds in seperate folder
Marios Nikolaou commented on JENKINS-13593 Seems to not handle having builds in seperate folder I am seeing the same issue in combination with other plugins such as the claim and disk usage plugins. We are using a separate workspace, build and JENKINS_HOME directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-18819) Unrecognized option -overwrite with 2002 version of ClearCase
Stéphane Bruckert closed JENKINS-18819 as Fixed Unrecognized option -overwrite with 2002 version of ClearCase Change By: Stéphane Bruckert (19/Jul/13 7:03 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Recently there was a new Gerrit Trigger plugin released: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/gerrit-trigger-2.10.0...gerrit-trigger-2.10.1 rinrinne Add provider attribute into gerrit events 151724c rinrinne Add trigger parameters using provider attribute in extended event I think there is a chance that it fixes integration with Gerrit 2.7 - need to be tested. 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] [scm-sync-configuration] (JENKINS-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Frédéric Camblor resolved JENKINS-15734 as Fixed NullPointerException in ScmSyncConfigurationPlugin.getInstance Should be fixed in upcoming 0.0.7.2 Change By: Frédéric Camblor (19/Jul/13 7:28 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.
[JIRA] [findbugs] (JENKINS-18836) java.io.IOException: Unexpected termination of the channel
Michiel Hendriks created JENKINS-18836 java.io.IOException: Unexpected termination of the channel Issue Type: Bug Assignee: Ulli Hafner Components: findbugs Created: 19/Jul/13 7:27 AM Description: On regular occasion builds fail due to an IO error while processing the findbugs results: 09:05:12 ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception 09:05:12 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel 09:05:12 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) 09:05:12 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) 09:05:12 at hudson.remoting.Request.call(Request.java:174) 09:05:12 at hudson.remoting.Channel.call(Channel.java:718) 09:05:12 at hudson.FilePath.act(FilePath.java:894) 09:05:12 at hudson.FilePath.act(FilePath.java:878) 09:05:12 at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161) 09:05:12 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:144) 09:05:12 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:334) 09:05:12 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 09:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 09:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) 09:05:12 at hudson.model.Build$BuildExecution.post2(Build.java:183) 09:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) 09:05:12 at hudson.model.Run.execute(Run.java:1618) 09:05:12 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 09:05:12 at hudson.model.ResourceController.execute(ResourceController.java:88) 09:05:12 at hudson.model.Executor.run(Executor.java:247) 09:05:12 Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel 09:05:12 at hudson.remoting.Request.abort(Request.java:299) 09:05:13 at hudson.remoting.Channel.terminate(Channel.java:778) 09:05:15 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) 09:05:15 Caused by: java.io.IOException: Unexpected termination of the channel 09:05:15 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) 09:05:16 Caused by: java.io.EOFException 09:05:16 at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2595) 09:05:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) 09:05:22 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) 09:05:22 at hudson.remoting.Command.readFrom(Command.java:92) 09:05:22 at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) 09:05:22 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This doesn't happen every time, sometimes the build does finish properly. But when it fails, it's always at the same point. None the less, I reverted back to 1.518 for now. Environment: Ubuntu 12.04 64bit, OpenJDK 1.6.0_27 (both master and slaves) Tried Jenkins versions 1.521, 1.522, 1.523 Project: Jenkins Priority: Major Reporter: Michiel Hendriks This message is automatically generated by JIRA. If you think it was sent incorrectly, please
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Frédéric Camblor resolved JENKINS-18715 as Fixed scandir being triggered by FingerPrint.save ok great PR will be available in upcoming 0.0.7.2 I'll try to release today Change By: Frédéric Camblor (19/Jul/13 7:30 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.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Could you add the user used by this plugin to "Non-Interactive Users" group in gerrit 2.7? 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] [scm-sync-configuration] (JENKINS-17201) SCM Sync page does not match current version (options explanations missing)
Frédéric Camblor resolved JENKINS-17201 as Fixed SCM Sync page does not match current version (options explanations missing) Fixed, but don't hesitate to update the wiki page by yourself I'm open to suggestions Change By: Frédéric Camblor (19/Jul/13 7:42 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.
[JIRA] [core] (JENKINS-8041) Archive the artifacts: custom name for archive.zip
Simon Didcote commented on JENKINS-8041 Archive the artifacts: custom name for archive.zip This would be very useful for me 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] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Before Gerrit 2.7, adding the jenkins user to "Non-Interactive Users" group was necessary too, so in the case when you upgrade Gerrit from 2.5 or 2.6 to 2.7 - the user should be already assigned to the proper group and no any additional step is needed. This is exactly my case - the user is already assigned to the "Non-Interactive Users" group. 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] [robot-plugin] (JENKINS-15768) Plug-in doesn't retain directories when copy files using Other files to copy setting
jpiironen started work on JENKINS-15768 Plug-in doesnt retain directories when copy files using Other files to copy setting Change By: jpiironen (19/Jul/13 8:05 AM) 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] [slave-setup] (JENKINS-18837) Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion)
Christo Zietsman created JENKINS-18837 Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion) Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 19/Jul/13 8:13 AM Description: We've got an old mac slave. After a recent upgrade of Jenkins I was unable to start a slave on this slave. It seems like the Jenkins slave is trying to load an incompatible class using the 1.5 jre. 07/17/13 15:16:33 SSH Checking java version of java 07/17/13 15:16:33 SSH java -version returned 1.5.0_13. 07/17/13 15:16:33 SSH Starting sftp client. 07/17/13 15:16:33 SSH Copying latest slave.jar... 07/17/13 15:16:33 SSH Copied 326,561 bytes. Expanded the channel window size to 4MB 07/17/13 15:16:33 SSH Starting slave process: cd '/hudson' java -jar slave.jar ===JENKINS REMOTING CAPACITY===channel started java.io.IOException: Remote call on mac failed at hudson.remoting.Channel.call(Channel.java:722) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:451) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:347) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:695) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:489) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassFormatError: Failed to load hudson.slaves.SlaveComputer$SlaveVersion at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:291) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:229) at java.lang.ClassLoader.loadClass(ClassLoader.java:316) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:113) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) 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:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:675) at java.lang.ClassLoader.defineClass(ClassLoader.java:520) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:289) ... 22 more Environment: Mac 10.5 Project: Jenkins Priority: Major Reporter: Christo Zietsman
[JIRA] [pathignore] (JENKINS-18838) Invert ignore? field gets unchecked after restarting the jenkins server.
costin doran created JENKINS-18838 Invert ignore? field gets unchecked after restarting the jenkins server. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: pathignore, plugin, ruby-runtime Created: 19/Jul/13 8:21 AM Description: Environment: 1 jenkins server with multiple slaves all jobs affected by this are executed by the same slave. All the jobs that have been configured to use the plugin and use the Invert ignore option, after restarting the jenkins, lose this setting. The invert ignore check box is unchecked after server restart. Project: Jenkins Priority: Major Reporter: costin doran 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-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Hmm...works fine on my below environments. Production Gerrit: 2.7-rc1 Jenkins: 1.523 Gerrit Trigger: 2.10.1 Jenkins start command: java -jar jenkins.war From gerrit-trigger repository Gerrit: 2.7-rc1 Jenkins: 1.424 Gerrit Trigger: 2.10.0 Jenkins start command: mvn hpi:run 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] [scm-sync-configuration] (JENKINS-18499) SCM-Sync No Longer synchronising job configurations (only the jenkins config.xml)
Frédéric Camblor closed JENKINS-18499 as Duplicate SCM-Sync No Longer synchronising job configurations (only the jenkins config.xml) Duplicate of JENKINS-18526 Change By: Frédéric Camblor (19/Jul/13 9:11 AM) Status: Open Closed 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] [warnings] (JENKINS-7178) Regular expression of Doxygen parser is too complex for JDK pattern
Ulli Hafner updated JENKINS-7178 Regular _expression_ of Doxygen parser is too complex for JDK pattern Change By: Ulli Hafner (19/Jul/13 9:15 AM) Summary: HudsonWarningPlugincrash,java.lang.StackOverflowError Regular_expression_ofDoxygenparseristoocomplexforJDKpattern 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-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Seems operation issue. Did you face this issue after gerrit connection is established? or connection has never been established after upgrading? If never established, you can try the below steps: 1. Visit "Gerrit Trigger" page in Jenkins. 2. Push "Stop" in the bottom. 3. Push "Start" in the bottom. 4. Reload page. And you should check gerrit log. (especially sshd_log). 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] [warnings] (JENKINS-18833) Doxygen Parser results in a fatal error
Ulli Hafner resolved JENKINS-18833 as Duplicate Doxygen Parser results in a fatal error I think the best approach would be to write a specific parser for Doxygen, see JENKINS-7178. Change By: Ulli Hafner (19/Jul/13 9:17 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
Ben Golding commented on JENKINS-13247 disk usage should not follow symlinks I think performance is important, but less important than correctness. Also isn't the disk usage calculation anyway running as a background thread? You may also consider that following a symlink to a directory potentially causes more files/dirs to be examined, so in those cases it will probably be faster overall, due to fewer total number of files/dirs. 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-18836) java.io.IOException: Unexpected termination of the channel
Ulli Hafner updated JENKINS-18836 java.io.IOException: Unexpected termination of the channel Seems more likely a core problem. In 1.519 a new class loader has been introduced. Maybe that is also the reason for your problem. How is your slave and master connected? ssh? Change By: Ulli Hafner (19/Jul/13 9:25 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18836) java.io.IOException: Unexpected termination of the channel
Michiel Hendriks commented on JENKINS-18836 java.io.IOException: Unexpected termination of the channel Yes, ssh slaves 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] [s3] (JENKINS-18839) S3 plugin fails to upload to EU region (wrong endpoint)
Stian Eikeland
created JENKINS-18839
S3 plugin fails to upload to EU region (wrong endpoint)
Issue Type:
Bug
Affects Versions:
current
Assignee:
Michael Watt
Components:
s3
Created:
19/Jul/13 9:30 AM
Description:
Uploading to a EU bucket fails using the new version of S3 plugin (v0.4) with the error:
ERROR: Failed to upload files
java.io.IOException: put Destination bucketName=, objectName=: Status Code: 301, AWS Service: Amazon S3, AWS Request ID: B731FD3EB3E36D68, AWS Error Code: PermanentRedirect, AWS Error Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint., S3 Extended Request ID: 1ayMHpR5YBq9DtqzPnBq5NdFR0Jn6kRbeaqrUPD4Ur+oUcL2vQlCiGbJSxjr9KXi
at hudson.plugins.s3.S3Profile.upload(S3Profile.java:85)
at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:143)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
at hudson.model.Run.execute(Run.java:1618)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:247)
Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE
It seems that this happen when you access the wrong amazon endpoint.
I've solved it temporarily for our setup by doing a: client.setEndpoint("s3-eu-west-1.amazonaws.com"); both places where AmazonS3Client is initialized in the S3 plugin (we only have EU buckets). There probably exist some easy way of querying for the correct endpoint for a more general solution.
Project:
Jenkins
Labels:
plugin
Priority:
Major
Reporter:
Stian Eikeland
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] [scm-sync-configuration] (JENKINS-16378) All build logs added and committed when renaming job
Frédéric Camblor commented on JENKINS-16378 All build logs added and committed when renaming job Have you tried with latest 0.0.7.1 ? Are you still facing the problem ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-18840) Remove support for Robot Framework split outputs.
Jussi Malinen created JENKINS-18840 Remove support for Robot Framework split outputs. Issue Type: Improvement Assignee: jpiironen Components: robot-plugin Created: 19/Jul/13 9:59 AM Description: Robot Framework 2.5 supported generating output.xml split into several files. Do we still need to support this option in Jenkins Plugin? This would simplify code. This option was removed in Robot 2.6, which came out 26.7.2011... Project: Jenkins Priority: Major Reporter: Jussi Malinen 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] [rvm] (JENKINS-18841) Failed loading job on slave because of incorrect config.xml
Mathias created JENKINS-18841 Failed loading job on slave because of incorrect config.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: rvm Created: 19/Jul/13 10:09 AM Description: I am using the rvm plugin to use the rvm environment on a slave instance of jenkins. I don't know when and why, but suddenly the config.xml of some jobs changes at the bottom to this: buildWrappers ruby-proxy-object ruby-object ruby-class="Jenkins::Plugin::Proxies::BuildWrapper" pluginid="rvm" object ruby-class="RvmWrapper" pluginid="rvm" launcher ruby-class="Jenkins::Launcher" pluginid="rvm" native ruby-class="Java::Hudson::RemoteLauncher" pluginid="rvm"/ /launcher rvm__path pluginid="rvm" ruby-class="String"/usr/local/rvm/scripts/rvm/rvm__path impl ruby-class="NilClass" pluginid="rvm"/ /object pluginid pluginid="rvm" ruby-class="String"rvm/pluginid /ruby-object /ruby-proxy-object /buildWrappers After a restart or reload of the config files jenkins won't load some jobs with the following error: SEVERE: Failed Loading job my_sweet_job hudson.util.IOException2: Unable to read /var/lib/jenkins/jobs/my_sweet_job/config.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: com.thoughtworks.xstream.converters.ConversionException: Undefined class: Java::Hudson::RemoteLauncher : Undefined class: Java::Hudson::RemoteLauncher Debugging information message : Undefined class: Java::Hudson::RemoteLauncher cause-exception : java.lang.IllegalArgumentException cause-message : Undefined class: Java::Hudson::RemoteLauncher class : org.jruby.runtime.builtin.IRubyObject required-type : org.jruby.runtime.builtin.IRubyObject converter-type : org.jenkinsci.jruby.JRubyXStreamConverter path: /project/buildWrappers/ruby-proxy-object/ruby-object/object/launcher/native line number : 128 class1: org.jenkinsci.jruby.JRubyMapper$DynamicProxy converter-type1 : org.jenkinsci.jruby.JavaProxyConverter class2: hudson.util.DescribableList converter-type2 : hudson.util.DescribableList$ConverterImpl class3: hudson.model.FreeStyleProject converter-type3 : hudson.util.RobustReflectionConverter version : null --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at org.jenkinsci.jruby.JRubyXStreamConverter.unmarshal(JRubyXStreamConverter.java:111) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at org.jenkinsci.jruby.JRubyXStreamConverter.unmarshal(JRubyXStreamConverter.java:111) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at
[JIRA] [sauce-ondemand] (JENKINS-18842) Starting URL field not being saved
Ross Rowe created JENKINS-18842 Starting URL field not being saved Issue Type: Bug Assignee: Ross Rowe Components: sauce-ondemand Created: 19/Jul/13 10:24 AM Description: Changes to the starting url field are not being stored within the Jenkins job configuration Project: Jenkins Priority: Major Reporter: Ross Rowe 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] [sauce-ondemand] (JENKINS-18842) Starting URL field not being saved
Ross Rowe started work on JENKINS-18842 Starting URL field not being saved Change By: Ross Rowe (19/Jul/13 10:44 AM) 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] [core] (JENKINS-14699) hg clone adding @2 to end of clone destination path
pedro reis commented on JENKINS-14699 hg clone adding @2 to end of clone destination path Hi, We're having today this "@2" problem for the first time at a Linux slave. Jenkins ver. 1.502 creates job workspace as "job@2" even when there is no "job" dir. 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] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
stanislav bashkirtsev commented on JENKINS-18377 Performance problem when listing many jobs I've raised issues with detailed analysis: JENKINS-18721 JENKINS-18723 They might be the reason of current 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] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
stanislav bashkirtsev edited a comment on JENKINS-18377 Performance problem when listing many jobs I've raised issues with detailed analysis: JENKINS-18721 JENKINS-18723 They might be the reason of current problem. RBAC is what makes the problem visible, but the problem itself is not in RBAC (at least that was what my analysis showed to me). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
stanislav bashkirtsev edited a comment on JENKINS-18377 Performance problem when listing many jobs I've raised issues with detailed analysis: JENKINS-18721 JENKINS-18723 They might be the reason of current problem. RBAC is what makes the problem visible, but the problem itself is not in RBAC (at least that was what my analysis showed to me), but in ListView. 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-14699) hg clone adding @2 to end of clone destination path
pedro reis commented on JENKINS-14699 hg clone adding @2 to end of clone destination path Thanks mat007! I confirm that Jenkins needs to be restarted in order to job@2 become job. Is there any easier way? 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-18843) Jenkins Wiping out workspace hudson.util.IOException2: remote file operation failed
Peter Goebel created JENKINS-18843 Jenkins Wiping out workspace hudson.util.IOException2: remote file operation failed Issue Type: Bug Assignee: Nicolas De Loof Attachments: taskManagerJenkinsSlave.png Components: git Created: 19/Jul/13 11:38 AM Description: Hi we get frequently an error like this on our jobs on jenkins slaves: Wiping out workspace first. hudson.util.IOException2: remote file operation failed: http://10.66.180.27:8080/job/Integration%20Flow%20Designtime%20Gerrit%20Voter/ws/ at hudson.remoting.Channel@44250147:Avt_veavjen007_Orange at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:877) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1108) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) 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:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: java.io.IOException: Unable to delete http://10.66.180.27:8080/job/Integration%20Flow%20Designtime%20Gerrit%20Voter/ws/.git\objects\pack\pack-c0af26544495cb6c77a6901bd276613f26e4c5a6.pack at hudson.Util.deleteFile(Util.java:256) at hudson.Util.deleteRecursive(Util.java:308) at hudson.Util.deleteContentsRecursive(Util.java:205 Our infrastructure consist of a Jenkins Master on Linux and slaves on Windows 2008 R2 Servers Attached you will find a screenshot of the task manager on the affected windows slave. Many ssh.exe, git.exe and some java.exe process run but should not run after a job is finished. What can we do to make jenkins killing the hanging processes? To fix this problem we tried one of the solution provide from the jenkins help page : https://issues.jenkins-ci.org/browse/JENKINS-15103 , included the parameter "-Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true" in the JVM options for the slave but it does not help. Could you please help us Best regards, Peter Project: Jenkins Priority: Critical Reporter: Peter Goebel 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-18844) Subversion SCMPolling does not work with Subversion Server 1.8 (SVNException)
Andy Grunwald created JENKINS-18844 Subversion SCMPolling does not work with Subversion Server 1.8 (SVNException) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 19/Jul/13 11:43 AM Description: Hey, if i enable SCMPolling as a mode for build triggering with an subversion servr 1.8 i got the exception: Jul 19, 2013 1:31:01 PM hudson.scm.SubversionSCM$CheckOutTask checkClockOutOfSync INFO: Failed to estimate the remote time stamp org.tmatesoft.svn.core.SVNException: svn: E210004: Number is larger than maximum at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:400) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:456) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:456) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:456) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:456) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readTuple(SVNReader.java:288) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:241) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:272) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1290) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.info(SVNRepositoryImpl.java:1203) at hudson.scm.SubversionSCM$CheckOutTask.checkClockOutOfSync(SubversionSCM.java:908) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:886) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath.act(FilePath.java:904) at hudson.FilePath.act(FilePath.java:877) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) 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:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: svn: E210004: Number is larger than maximum at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readItem(SVNReader.java:399) ... 24 more Environment: FreeBSD 9 Jenkins ver. 1.514 Subversion Server 1.8 Jenkins Subversion Plug-in 1.50 Project: Jenkins Priority: Major Reporter: Andy Grunwald 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] [robot-plugin] (JENKINS-18675) Failure in suite teardown does not fail test cases
Jussi Malinen resolved JENKINS-18675 as Fixed Failure in suite teardown does not fail test cases Fixed. Change By: Jussi Malinen (19/Jul/13 11:51 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.
[JIRA] [robot-plugin] (JENKINS-16158) Delete button disappeared
Jussi Malinen commented on JENKINS-16158 Delete button disappeared Which Jenkins version are you using? 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 created JENKINS-18845 Jenkins 1.522 - Repository Browser Sventon is gone Issue Type: Bug Assignee: Unassigned Attachments: 19-07-2013_13-45-33_RepositoryBrowserJenkins.png Components: subversion Created: 19/Jul/13 12:04 PM Description: In the Jenkins(1.522) Job Configuration - Source Code Management - Subversion there is no Repository Browser "Svention 2.x" selectable. The attached picture is showing the old and the current range of functionality. Is the support of Sventon deactivated or is it a Bug? Environment: Windows XP, Jenkins 1.522, Sventon 2.1.3 Project: Jenkins Priority: Minor Reporter: Tom Sch 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-18846) New lazy loading permalinks can break job.lastStableBuild != null = job.lastSuccessfulBuild != null
stephenconnolly created JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null = job.lastSuccessfulBuild != null Issue Type: Bug Assignee: Unassigned Components: core, maven Created: 19/Jul/13 12:11 PM Description: I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am` The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined. The individual MavenModule instances, however, will only have lastStable defined. Project: Jenkins Priority: Major Reporter: stephenconnolly 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-18844) Subversion SCMPolling does not work with Subversion Server 1.8 (SVNException)
Andy Grunwald commented on JENKINS-18844 Subversion SCMPolling does not work with Subversion Server 1.8 (SVNException) svnkit 1.8 is available http://svnkit.com/download.php 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] [robot-plugin] (JENKINS-14366) Robot plugin doesn't handle suite names properly when multiple suites are being ran
Jussi Malinen commented on JENKINS-14366 Robot plugin doesnt handle suite names properly when multiple suites are being ran Sorry for late reply, we are working on this plugin again. Is this still an issue for you? Could you send an example output.xml that demonstrates the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11186) Jenkins hangs while producing testReport
Martin Heinrich commented on JENKINS-11186 Jenkins hangs while producing testReport cannot reproduce behaviour from my previous comment with Jenkins ver. 1.523. 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] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project This looks like it will work - it is a bit cumbersome though and will need to be done by hand for any multi-configuration project that uses RTC. Are you planning a solution in the RTC plugin to prevent a checkout in the main job or some other solution that does not require this manual fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18847) FishEye No Longer Recognized (or Shown) for Subversion Repository Browser
John Werner created JENKINS-18847 FishEye No Longer Recognized (or Shown) for Subversion Repository Browser Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 19/Jul/13 12:50 PM Description: The selection for "FishEye" under Subversion/Repository Browser is no longer available. Additionally, the configuration is no longer recognized in existing projects. The following is logged when a job with it configured is loaded: Jul 19, 2013 8:18:54 AM hudson.util.RobustReflectionConverter doUnmarshal WARNING: Failed to resolve a type java.lang.InstantiationError: hudson.scm.SubversionRepositoryBrowser at sun.reflect.GeneratedSerializationConstructorAccessor351.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.thoughtworks.xstream.converters.reflection.Sun14ReflectionProvider.newInstance(Sun14ReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:376) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at hudson.XmlFile.read(XmlFile.java:143) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$17.run(Jenkins.java:2542) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Environment: Windows Server Project: Jenkins Priority: Major
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I tried this and in fact it does not seem to work? Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... FATAL: RTC : checkout failure: Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob com.ibm.team.filesystem.client.FileSystemStatusException: Status ERROR: com.ibm.team.filesystem.client code=0 Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob null at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:1) at com.ibm.team.filesystem.client.internal.SharingManager.register(SharingManager.java:1002) at com.ibm.team.build.internal.hjplugin.rtc.RepositoryConnection.checkout(RepositoryConnection.java:363) at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.checkout(RTCFacade.java:387) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory$RTCFacadeWrapper.invoke(RTCFacadeFactory.java:92) at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:107) at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:31) at hudson.FilePath.act(FilePath.java:906) As you can see the 2 checkout directories are adjacent and not nested but it still complains about the sandbox (maybe because they are both using the same repository workspace)? 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
Jeroen Mostert commented on JENKINS-18312 changelog browsing uses the wrong path to Redmine I compared PR https://github.com/jenkinsci/redmine-plugin/pull/10 with my patch and as far as I can see this should result in the same links to redmine. 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] [cvs] (JENKINS-18539) CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6
Florian Rosenauer commented on JENKINS-18539 CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6 Reducing priority is fine if v1.6 API is still supported. We are running 790 jobs in total, about 95% using CVS. We have 4 slaves (139, 137, 14, 20 jobs), the rest is on master. Master has 4 executors, each slave 1 executor. Concurrent SCM polling is limited to 5. Jobs polling was "0,30 6-22 * * *" and is now H 6-22 * * * (but that didn't really change the load). Nightly builds run with "00 02 * * 1-5". The "Disable CVS compression" checkbox is not active. When I had installed 2.9 I didn't make any changes to the default value (I think it was "default: 3"). But can the change to rlog really increase the load by 10 times? 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-17941) Parse errors with Git's TAP test suite
SCM/JIRA link daemon commented on JENKINS-17941 Parse errors with Gits TAP test suite Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapTestResultAction.java http://jenkins-ci.org/commit/tap-plugin/4b259118ffc024a99c4cedf1bc13bfdae993440f Log: JENKINS-17941 Fixing test diff string 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Ronald Müller created JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Issue Type: Bug Affects Versions: current Assignee: Timothy Bingaman Components: ivy Created: 19/Jul/13 1:24 PM Description: After upgrade to: Jenkins 1.523 Ivy-Plugin 1.23.1 All Ivy-Projects will not build anymore and ends up with a NPE. Checkout from SVN is fine so far: Building in workspace /var/lib/jenkins/jobs/graphicsUtility/workspace Cleaning local Directory . Checking out svn+ssh://ziv@uz-labor/var/svn/java-libs/graphicsUtility/trunk at revision '2013-07-19T15:06:03.638 +0200' ... U. At revision 752 no change for svn+ssh://ziv@uz-labor/var/svn/java-libs/graphicsUtility/trunk since the previous build ERROR: Processing failed due to a bug in the code. Please report this to us...@hudson.dev.java.net java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:239) at hudson.FilePath.resolvePathIfRelative(FilePath.java:224) at hudson.FilePath.init(FilePath.java:220) at hudson.FilePath.child(FilePath.java:1133) at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:372) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.Run.run(Run.java:1539) at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:281) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) project=hudson.ivy.IvyModuleSet@17feafbagraphicsUtility project.getModules()=[hudson.ivy.IvyModule@72a32604graphicsUtility/de.unicomp:graphicsUtility] FATAL: null java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:239) at hudson.FilePath.resolvePathIfRelative(FilePath.java:224) at hudson.FilePath.init(FilePath.java:220) at hudson.FilePath.child(FilePath.java:1133) at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:372) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.Run.run(Run.java:1539) at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:281) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Due Date: 19/Jul/13 12:00 AM Environment: Ubuntu LTS 12.04 Project: Jenkins Priority: Major Reporter: Ronald Müller 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita commented on JENKINS-17941 Parse errors with Gits TAP test suite 2) Slightly below, there's the text "This build contains 628 TAP test sets. Click here for details" and "1 parse error(s)". Again I'm not sure what causes the parse error, whether it's a bug in the TAP plugin or a bug it Git's test suite output. In any case it would be nice to see the name of the (sub-)test where the error occurred here. I believe that information is available in the build summary (the "Click here" link points to that page). Not sure if we should add that information in the project page, since it can contain a long list when many TAP streams failed to be parsed. Perhaps it could be added as a feature... since other users could find useful to have a list of failed tests... or bail out'ed tests. I believe the TAP Stream of that parser error is this one: https://qa.nest-initiative.org/view/msysGit/job/msysgit-mingwGitDevEnv-test/125/tapResults/contents?f=test-results/t9200-git-cvsexportcommit.sh I think the plug-in was right to fail to parse it. However, I had to manually enter the file name in the browser URL to view the file that the plug-in failed to parse. Commit 22dff5c9899056a3df0ea69b2bc8ff17a1d0c4a8 adds a link to that file. 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-17941) Parse errors with Git's TAP test suite
SCM/JIRA link daemon commented on JENKINS-17941 Parse errors with Gits TAP test suite Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/org/tap4j/plugin/TapResult/index.jelly http://jenkins-ci.org/commit/tap-plugin/22dff5c9899056a3df0ea69b2bc8ff17a1d0c4a8 Log: JENKINS-17941 Adding link to view file that failed to be parsed 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita commented on JENKINS-17941 Parse errors with Gits TAP test suite Hello Sebastian! How's it going? Fixed two other issues in tap-plugin, now working on this one again 1) That page contains the string "TAP Test Result (130 failures null)", not sure why "null" is in there. However, the total number of 130 failed tests is correct, that's the same number I'm calculating in my Groovy post-build script. The Groovy script also generates the output below "The following test(s) failed" on that page, which is my reference for the list of failing tests. I didn't recall what that "null" was supposed to be, so I had to check Jenkins core source code. That's the diff string. It used the previous build (if it had TAP tests) to compute the diff. I didn't override the AbstractTestResultAction#getPreviousResult() method and it wasn't being able to find the previous builds. I believe it has been fixed in 4b259118ffc024a99c4cedf1bc13bfdae993440f. Moving on to the next item... 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-17941) Parse errors with Git's TAP test suite
SCM/JIRA link daemon commented on JENKINS-17941 Parse errors with Gits TAP test suite Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/org/tap4j/plugin/TapBuildAction/summary.jelly src/main/resources/org/tap4j/plugin/TapResult/index.jelly http://jenkins-ci.org/commit/tap-plugin/7cab81f801c34a106b12391e04615e0ad1df5347 Log: JENKINS-17941 Modify tapResults text on the UI. Was Tap test results, now Extended TAP Test Results 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita updated JENKINS-17941 Parse errors with Gits TAP test suite Test diff and new tapResults text Change By: Bruno P. Kinoshita (19/Jul/13 1:37 PM) Attachment: 17941-1.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] [tap] (JENKINS-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita edited a comment on JENKINS-17941 Parse errors with Gits TAP test suite 3) The "TAP Test Result" from 1) and the "Click here for details" from 2) link to 4 and 5 respectively. At first I was confused that the TAP plugin provides two detailed results pages, and I'm still not sure whether this makes sense. Got it, you're right indeed. Added a screenshot showing the fixed test diff and the new text in the project page (it was altered in the build page too). It was Tap Test Result, and you had to click on a Click "here" link to go to the page. Now there's a link (mimicking the behaviour of the other test result), but the name was changed to Extended TAP Test Results. What do you think? 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita edited a comment on JENKINS-17941 Parse errors with Gits TAP test suite 3) The "TAP Test Result" from 1) and the "Click here for details" from 2) link to 4 and 5 respectively. At first I was confused that the TAP plugin provides two detailed results pages, and I'm still not sure whether this makes sense. Got it, you're right indeed. Added a screenshot showing the fixed test diff and the new text in the project page (it was altered in the build page too). It was Tap Test Result, and you had to click on a Click "here" link to go to the page. Now there's a link (mimicking the behaviour of the other test result), but the name was changed to Extended TAP Test Results. What do you think? Screenshot https://issues.jenkins-ci.org/secure/attachment/24018/17941-1.png Fixed in commit 7cab81f801c34a106b12391e04615e0ad1df5347 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-18849) java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject
Joshua Slominski created JENKINS-18849 java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.log, Screen shot 2013-07-19 at 9.23.00 AM.png Components: maven Created: 19/Jul/13 1:43 PM Description: I upgraded to 1.509.2. Now, the post build actions of the configure page is not displaying and giving an error 500. The Jenkins log is full of java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject. Screen shots and logs attached NOTE: I downgraded back to 1.509.1 but the error still exists. Environment: RHEL Project: Jenkins Priority: Major Reporter: Joshua Slominski 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita commented on JENKINS-17941 Parse errors with Gits TAP test suite 4) On 4, clicking on any if the "" or test links under "All Failed Tests" results in "Status Code: 404". Also, the list of "All Failed Tests" does not seem to be correct as it includes the tests marked as "TODO known breakage". Maybe you could add an option to ignore results of tests marked as TODO? I'm also a bit confused why our total failed test count of 130 matches mine, although you count "TODO known breakage" as failures and I don't. I spotted this bug while working on another issue few days ago, but I have a meeting within moments and can't look which commit is it in :-/ sorry. But in short, I removed the link, since you can see the TAP test by clicking on its name. Hope that works for you 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] [build-publisher] (JENKINS-18850) doCheckHudsonUrl fails to consider authentication
Jesse Glick created JENKINS-18850 doCheckHudsonUrl fails to consider authentication Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 19/Jul/13 1:57 PM Description: BuildPublisherPlugin.doCheckHudsonUrl calls HudsonURL, which is useless since it does not consider authentication. Assuming that the public Jenkins server uses authentication—which is almost certain—this form validation can never work; it is just misleading and would be better deleted than left in its current state. Probably what you want is for BuildPublisher.BuildPublisherDescriptor to have a doCheckUrl method that uses multiple @QueryParameter arguments to load also login and password fields. global.jelly may need to simplified/normalized to use the field attribute, ideally with HudsonInstance getting its own config.jelly page that gets inserted automatically by f:repeatableProperty. Not sure about all the details here (tried in https://github.com/jenkinsci/jenkins/pull/816 but did not get everything working). Alternately, continue to manually encode the textbox values (though this will not trigger correct logic for retrying validation after edits). Project: Jenkins 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] [database] (JENKINS-18817) Executing Oracle Database scripts after the build
Srikanth Tirukovalluru commented on JENKINS-18817 Executing Oracle Database scripts after the build Please help regarding this 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] [sauce-ondemand] (JENKINS-18842) Starting URL field not being saved
dsheth commented on JENKINS-18842 Starting URL field not being saved I reported this issue to Ross...and I want to clarify one point of this issue: 1. if selenium rc is selected: the url is saved. 2. web driver selected--the field itself goes away 3. If the page is opened again, the web driver is still selected, and the field is present 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-jira-issue-updater] (JENKINS-18835) Exception after upgrade to version 1.514 from 1.488
Kunal Chaturvedi resolved JENKINS-18835 as Fixed Exception after upgrade to version 1.514 from 1.488 Resolved by updating the config.xml again. Change By: Kunal Chaturvedi (19/Jul/13 2:13 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] [tap] (JENKINS-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita
commented on JENKINS-17941
Parse errors with Gits TAP test suite
Broke item 5 into four parts. Please, find the comments below:
5) On 5, test marked as "TODO known breakage" are also marked red, i.e. as failures, but again the total number of failed tests oddly is correct. But the number of skipped tetsts is not. The header says "628 files 9549 tests, 8967 ok, 130 not ok, 1 skipped, 0 Bail Out!", but as you can see from the yellow entries in the table there are far more than 1 skipped tests.
Hmmm. Weird. I imported test-results/t-basic.sh into my dev-workspace (hope you don't mind it). And the plug-in successfully reported "7 skipped,"... Looking at the code, though, I found a bug in the TapResult#tally() method:
snippet
if (plan.isSkip()) {
this.skipped = testResults.size();
} else {
for (TestResult testResult : testResults) {
if (isSkipped(testResult)) {
skipped += 1;
} else if (isFailure(testResult)) {
failed += 1;
} else {
passed += 1;
}
}
}
/snippet
zooming-in
if (plan.isSkip()) {
this.skipped = testResults.size();
}
}
/zooming-in
I hope you understand what I'm highlighting here. If the plan was marked with SKIP for any reason, the skip count would be reset. Say you had 1 test in that Test Set. Possibly, you would have 1 Skipped test being incorrectly displayed.
Normal tests running (after importing your TAP stream):
60 tests, 52 ok, 1 not ok, 7 skipped, 0 Bail Out!.
Running again, after adding a Test Set with 10 tests, with the Plan marks them all as SKIP.
70 tests, 52 ok, 1 not ok, 10 skipped, 0 Bail Out!.
After fixing the tally method (now it's: skipped += testResults.size()
70 tests, 52 ok, 1 not ok, 17 skipped, 0 Bail Out!.
Hopefully it'll fix your issue. I tried to find a plan with SKIP on your build... but there were too many files to look for.
Also, whenever there's a comment in the raw TAP file, you make it part of the table. I think the plugin should simply ignore lines starting with "#" in the input files and not include them into the table. A good example on that page is at "test-results/t5801-remote-helpers.sh" where you see a lot of comments which should not be visible at all, IMHO.
Deal, I'll add a new feature while working on issue JENKINS-18703 or JENKINS-17804.
The bottom of the page finally contains the details about parse errors, which is great. Maybe the "1 parse error(s)" from the overview page could link here? In any case I like this result page much better than 4, and I'd like to suggest to completely drop 4 and just fix the issues with 5 instead. This will also lead to less confusion for the user which TAP result page to look at.
Good idea mate. Added a a name='parseErrors' / just before the Parse errors section. Now if you type
http://localhost:8080/job/test-17941/3/tapResults/#parseErrors
in your browser URL you'll see the parse errors. I've also added a link the build page that goes direct to this section.
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-17941) Parse errors with Git's TAP test suite
Sebastian Schuberth commented on JENKINS-17941 Parse errors with Gits TAP test suite 2) Slightly below, there's the text "This build contains 628 TAP test sets. Click here for details" and "1 parse error(s)". Again I'm not sure what causes the parse error, whether it's a bug in the TAP plugin or a bug it Git's test suite output. In any case it would be nice to see the name of the (sub-)test where the error occurred here. I believe that information is available in the build summary (the "Click here" link points to that page). Not sure if we should add that information in the project page, since it can contain a long list when many TAP streams failed to be parsed. Perhaps it could be added as a feature... since other users could find useful to have a list of failed tests... or bail out'ed tests. I agree that the information itself should not be duplicated on that page. What I was thinking about was more like adding an anchor like https://qa.nest-initiative.org/view/msysGit/job/msysgit-mingwGitDevEnv-test/125/tapResults/#parse_errors and linking the "1 parse error(s)" text on https://qa.nest-initiative.org/view/msysGit/job/msysgit-mingwGitDevEnv-test/125/ to that anchor, so you can directly jump to that section of the TAP results. I think the plug-in was right to fail to parse it. However, I had to manually enter the file name in the browser URL to view the file that the plug-in failed to parse. I agree that it's correct to report a parse error in this case. Thanks for adding that direct link to the offending file! 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-17941) Parse errors with Git's TAP test suite
Bruno P. Kinoshita commented on JENKINS-17941 Parse errors with Gits TAP test suite Ops, just read your comment... I think I was following top-down your comments, and thus only added the parseErrors while reading item 5)... anyway, funny coincidence time to have lunch and... attend all the meetings o/ Let me know if you need anything else, feel free to re-open it later if I missed anything, or report new issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17941) Parse errors with Git's TAP test suite
SCM/JIRA link daemon commented on JENKINS-17941 Parse errors with Gits TAP test suite Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapResult.java src/main/resources/org/tap4j/plugin/TapBuildAction/summary.jelly src/main/resources/org/tap4j/plugin/TapResult/index.jelly http://jenkins-ci.org/commit/tap-plugin/a0cf096db375ad5dc28c2d51bc3b209cb4d9e6c8 Log: FIXED JENKINS-17941 Added handy parseErrors link to the build page. Fixed skipped counter. Added more awesomeness to the plug-in, thanks to Sebastian Schuberth 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] [sauce-ondemand] (JENKINS-18842) Starting URL field not being saved
dsheth edited a comment on JENKINS-18842 Starting URL field not being saved How to reproduce: 1. Open job config. 2. Select selenium rc, set starting url, and save 3. Open job config--the starting url will be in place 4. Select web driver--the starting url field disappears 5. Save 6. Open job config: starting url field present and empty This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-jira-issue-updater] (JENKINS-18835) Exception after upgrade to version 1.514 from 1.488
Kunal Chaturvedi closed JENKINS-18835 as Fixed Exception after upgrade to version 1.514 from 1.488 Change By: Kunal Chaturvedi (19/Jul/13 2:13 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] [sauce-ondemand] (JENKINS-18842) Starting URL field not being saved
dsheth edited a comment on JENKINS-18842 Starting URL field not being saved How to reproduce: 1. Open job config. 2. Select selenium rc, set starting url, and save 3. Open job config--the starting url will be in place 4. Select web driver--the starting url field disappears 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-17855) TAP Stream results summary page contains links that fail
Bruno P. Kinoshita stopped work on JENKINS-17855 TAP Stream results summary page contains links that fail Change By: Bruno P. Kinoshita (19/Jul/13 2:22 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17941) Parse errors with Git's TAP test suite
SCM/JIRA link daemon resolved JENKINS-17941 as Fixed Parse errors with Gits TAP test suite Change By: SCM/JIRA link daemon (19/Jul/13 2:18 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] [ssh-slaves] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
mcmenace mcmenace edited a comment on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell Same problem here! Is there a workaround or a fix in an upcoming version? Currently running jenkins 1.523 with ssh-slave-plugin 0.27 in a bitnami virtualbox VM. Connection to linux 32/64bit and MacOS via ssh works perfect. Connections to WinXp and Win8 running Bitvise SSH server yield: 07/19/13 14:14:29 SSH Opening SSH connection to itchy.imp.fu-berlin.de:22. 07/19/13 14:14:29 SSH Authentication successful. SSH connection reports a garbage before a command execution. Check your .bashrc, .profile, and so on to make sure it is quiet. The received junk text is as follows: 'true' is not recognized as an internal or external command, operable program or batch file. hudson.AbortException at hudson.plugins.sshslaves.SSHLauncher.verifyNoHeaderJunk(SSHLauncher.java:613) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:490) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) 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) 07/19/13 14:14:29 SSH Connection closed. Has some any ideas how to debug? Command execution via ssh on the command line (bash) from a linux maschine to WinXp and Win8 boxes work without any garbage returned. Cheers McMenace ps: If I can help or anyone needs more information please let me know. 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-publisher] (JENKINS-18851) HudsonInstance.password stored in plaintext
Jesse Glick created JENKINS-18851 HudsonInstance.password stored in plaintext Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 19/Jul/13 2:32 PM Description: HudsonInstance.password should be persisted as a Secret, not a String. Project: Jenkins Labels: security 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] [tap] (JENKINS-17941) Parse errors with Git's TAP test suite
Sebastian Schuberth commented on JENKINS-17941 Parse errors with Gits TAP test suite Let me know if you need anything else, feel free to re-open it later if I missed anything, or report new issues. Thanks a lot for your responsiveness and all the fixes! I'll test your improvements as soon as your plugin has a new release that I can install via Jenkins' update mechanism (I do not have admin access on that Jenkins so I need to wait for an "official" update of your plugin). I'll file new tickets in case I find more issues because this one is already getting a bit crowded Thanks 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] [ssh-slaves] (JENKINS-15746) Cannot run SSH commands on SSH servers that use Windows shell
mcmenace mcmenace commented on JENKINS-15746 Cannot run SSH commands on SSH servers that use Windows shell Same problem here! Is there a workaround or a fix in an upcoming version? Currently running jenkins 1.523 with ssh-slave-plugin 0.27 in a bitnami virtualbox VM. Connection to linux 32/64bit and MacOS via ssh works perfect. Connections to WinXp and Win8 running Bitvise SSH server yield: 07/19/13 14:14:29 SSH Opening SSH connection to itchy.imp.fu-berlin.de:22. 07/19/13 14:14:29 SSH Authentication successful. SSH connection reports a garbage before a command execution. Check your .bashrc, .profile, and so on to make sure it is quiet. The received junk text is as follows: 'true' is not recognized as an internal or external command, operable program or batch file. hudson.AbortException at hudson.plugins.sshslaves.SSHLauncher.verifyNoHeaderJunk(SSHLauncher.java:613) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:490) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) 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) 07/19/13 14:14:29 SSH Connection closed. Has some any ideas how to debug? Command execution via ssh on the command line (bash) from a linux maschine to WinXp and Win8 boxes work without any garbage returned. Cheers McMenace 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-18805) Gerrit Triger fails on vote
rin_ne commented on JENKINS-18805 Gerrit Triger fails on vote Perhaps your provided log has nothing to do with this issue. Because logged exception occurs from _javascript_ error in manual trigger page. 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-17941) Parse errors with Git's TAP test suite
Sebastian Schuberth commented on JENKINS-17941 Parse errors with Gits TAP test suite It was Tap Test Result, and you had to click on a Click "here" link to go to the page. Now there's a link (mimicking the behaviour of the other test result), but the name was changed to Extended TAP Test Results. What do you think? Thanks, I think that's much clearer than before. But still, for my personal taste, only having what is now called "TAP Extended Test Results" would be enough, and you could get rid of generating the "TAP Test Results" page at all. I like that colorful table much better than that other expandable / collapsible table 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-17855) TAP Stream results summary page contains links that fail
Bruno P. Kinoshita resolved JENKINS-17855 as Fixed TAP Stream results summary page contains links that fail Hello Alex! I've fixed this issue while working on another issue few days ago. I was fixing the bug and spotted and included that fix in the same commit message. I can't recall which commit it was, but I believe it'll be fixed in the next release. Let me know if it doesn't work. All the best, and thanks again! /B Change By: Bruno P. Kinoshita (19/Jul/13 2: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] [warnings] (JENKINS-18852) Warnings plugin displays two copies of warnings graph
mwebber created JENKINS-18852 Warnings plugin displays two copies of warnings graph Issue Type: Bug Assignee: Ulli Hafner Attachments: config.xml Components: warnings Created: 19/Jul/13 3:15 PM Description: I have several jobs that use the Warnings plugin. When I look at the job page, I see 4 graphs on the roght-hand side, bearing the following 4 legends (above the graph in each case): Buckminster Warnings Trend Compiler Warnings Trend Open Tasks Trend Test Result Trend There should only be 3 graphs. The top two are reporting duplicate information. I think it changed to 4 graphs when I updated: analysis-core@1.49 -- analysis-core@1.50 warnings@4.26 -- warnings@4.27 This looks like it has happened in every job that uses the warnings plugin. I have attached a copy of a config that has the problem. Project: Jenkins Priority: Major Reporter: mwebber 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
SCM/JIRA link daemon commented on JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Code changed in jenkins User: Stéphane Bruckert Path: src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/3ce366a17835bbc73400d3dd4a9bb140cebf7bf4 Log: JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION https://issues.jenkins-ci.org/browse/JENKINS-18609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel 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] [cas] (JENKINS-18853) CAS plugin for Jenkins doesn't honor --prefix
Nathan Graham created JENKINS-18853 CAS plugin for Jenkins doesnt honor --prefix Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cas Created: 19/Jul/13 3:45 PM Description: I tried to use mod_proxy to forward requests from http://server/jenkins to http://server:8080 (as per https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache?focusedCommentId=63146343#comment-63146343). This worked fine for the most part except that the CAS plugin (https://wiki.jenkins-ci.org/display/JENKINS/CAS+Plugin CAS plugin) appears to forget the /jenkins prefix when returning from authentication. For example, when I visit http://server/jenkins/ I'm correctly forwarded to our CAS login page, but when I'm redirected back to Jenkins, the URL is something like http://server:8080/securityRealm/finishLogin?ticket=... (it's missing the /jenkins prefix). I believe it should be http://server:8080/jenkins/securityRealm/finishLogin?ticket= In fact, when I manually modify the URL to include /jenkins (after being erroneously forwarded to the wrong address) the login is successful and I can interact with Jenkins normally. If I don't use mod_proxy (and visit http://server:8080 directly) the CAS plugin works well. Environment: SUSE Linux Project: Jenkins Labels: plugin cas Priority: Major Reporter: Nathan Graham 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] [ec2] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
Colby Dyess created JENKINS-18854 EC2 Plugin unable to connect to Eucalyptus 3.x Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 19/Jul/13 3:49 PM Description: The EC2 plugin is unable to successfully connect to any Eucalyptus 3.x cloud. The EC2 plugin currently requests a single URL Eucalytpus_URL/register which it calls in order to obtain the EC2 and S3 endpoints. The trouble immediately hits when the EC2 plugin attempts to use the AWS Java SDK to connect to Eucalyptus. The specific issue is that the AWS Java SDK requires a trailing "/" to successfully connect. For example: http://eucalyptus.mycloud.com/services/Eucalyptus is what is returned from the /register call. But this: http://eucalyptus.mycloud.com/services/Eucalyptus/ is what the SDK needs. It should be noted that the /register endpoint is deprecated. Eucalyptus created that service call for a specific partner integration. The endpoint is no longer required by that partner and there are no plans to maintain it. The resolution should ensure the EC2 plugin a) successfully connects and b) does not require the /register endpoint. Environment: Current Jenkins Eucalyptus 3.x Project: Jenkins Priority: Blocker Reporter: Colby Dyess 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] [pending-changes] (JENKINS-18856) Pending changes doesn't honor SVN excluded regions
Bryce Schober created JENKINS-18856 Pending changes doesnt honor SVN excluded regions Issue Type: Bug Assignee: Unassigned Components: pending-changes Created: 19/Jul/13 4:01 PM Description: It sure would be nice if the pending changes view filtered changes with only SVN excluded regions, like the SVN SCM plugin does. Project: Jenkins Priority: Major Reporter: Bryce Schober 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-17859) TAP report table show failed test message on ALL tests after the failed one.
Bruno P. Kinoshita commented on JENKINS-17859 TAP report table show failed test message on ALL tests after the failed one. Hi again Moshe. Just confirmed it was a critical bug in tap4j 1. Fixed in 2. Will cut a new release of tap4j tonight, as well as a new tap-plugin version tonight or tomorrow morning (since it 1 https://github.com/tupilabs/tap4j/issues/14 2 https://github.com/tupilabs/tap4j/commit/196088760ef63443aea444f750a613b41e3f1733 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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException in global-build-stats plug-in at startup
Kevin Calman assigned JENKINS-17248 to Frédéric Camblor java.lang.NullPointerException in global-build-stats plug-in at startup Change By: Kevin Calman (19/Jul/13 5:29 PM) Assignee: FrédéricCamblor 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
SCM/JIRA link daemon commented on JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/96024dab2ceb2c405c7b41efee7a2bbc4f2ac46f Log: Merge pull request #72 from stephanebruckert/patch-3 JENKINS-18609 Triggers two mails: UNSTABLE and IMPROVEMENT Compare: https://github.com/jenkinsci/email-ext-plugin/compare/a960c649f7ac...96024dab2ceb 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert resolved JENKINS-18609 as Fixed Triggers two mails: UNSTABLE and REGRESSION Change By: Stéphane Bruckert (19/Jul/13 3:34 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
SCM/JIRA link daemon commented on JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Code changed in jenkins User: Stéphane Bruckert Path: src/main/java/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/cd14755f2eafcb0110b140cc7de51cd1ba6f03b1 Log: JENKINS-18609 Triggers two mails: UNSTABLE and IMPROVEMENT The improvement trigger is only triggered when there are LESS failing tests. It implies being UNSTABLE or STILL UNSTABLE. Otherwise it would be SUCCESS or FIXED. This modification makes the IMPROVEMENT trigger overriding the UNSTABLE or STILL UNSTABLE triggers. 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] [sauce-ondemand] (JENKINS-17687) Sauce-ondemand times out every time
David Brochu commented on JENKINS-17687 Sauce-ondemand times out every time I also see the same issue in my environment 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] [msbuild] (JENKINS-18560) Extra when forming cmd line arguments for parameters containing a space
Jonathan Zimmerman commented on JENKINS-18560 Extra when forming cmd line arguments for parameters containing a space This is a duplicate of JENKINS-18543. 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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Kevin Calman commented on JENKINS-17248 java.lang.NullPointerException by start I am experiencing this issue too. I have Hudson 2.2.1 installed on CentOS 5.4 typically and it has been working fine for months, since the last version upgrade. I have not added or updated any plugins in the last several weeks, and have restarted the service and rebooted the machine since any configuration changes and all was working. Today, I restarted the service and experienced this issue. I manually removed the global-build-stats plug-in and restart, and it worked. From the Hudson web interface, I re-installed the global-build-stats v1.3 and set the service to restart when no jobs were running, and the issue reappeared. I have to again manually remove the global-build-stats plug-in and run without until this issue is resolved. Status? Can I provide any more info that would be useful? 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(19/Jul/13 3:08 PM)
Environment:
Jenkins1.513Email-ext2.28
DefaultemailpluginE-mailNotificationisNOTactivated.Thisisasurefact.
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible(seescreenshot).ButIreceivedtwoemailsforthesamebuild.IMHO,thisisnottheexpectedbehavior(oritisabug)becauseabuildwithREGRESSIONSinevitablymeansthatthebuildisUNSTABLE.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.
ThesameappliestoSTILLUNSTABLE.
Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{code:title=RegressionTrigger.java|borderStyle=solid}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);
addTriggerNameToReplace(StillUnstableTrigger.TRIGGER_NAME);
}{code}Iamwaitingforyoutoagreethatthisisabug,beforelettingmecorrectitontherepository,ifyouagree.Thankyouverymuch!
Edit:ItisthesamebetweentheStillUnstableandImprovementtriggers:{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:ImprovementEmailwastriggeredfor:StillUnstableTriggerUnstablewasoverriddenbyanothertriggerandwillnotsendanemail.Sendingemailfortrigger:StillUnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:ImprovementSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}TheimprovementtriggerisonlytriggeredwhenthereareLESSfailingtests.SoitismeanttobeUNSTABLEorSTILLUNSTABLE.OtherwiseitwouldbeSUCCESSorFIXED.
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] [jobgenerator] (JENKINS-18663) Generator triggers the build step using conditional build step
Walter Kacynski closed JENKINS-18663 as Fixed Generator triggers the build step using conditional build step This problem has been fixed. Change By: Walter Kacynski (19/Jul/13 5:52 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] [msbuild] (JENKINS-18543) Update to newest MSBuild plugin breaks passing of release configurations with spaces in them
Jonathan Zimmerman commented on JENKINS-18543 Update to newest MSBuild plugin breaks passing of release configurations with spaces in them When I authored the fix for that issue I included unit tests that were supposed to verify proper functionality. Unfortunately things get mangled further along when the external process is actually launched. I think in my case escaping the quotes around the parameter value may solve the problem, so I'll revert the break from my previous commit and look for another way around the previous 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] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Christian Höltje commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem with Jenkins 1.509.2 and Copy Artifacts 1.27 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] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes commented on JENKINS-16158 Delete button disappeared I've been upgrading Jenkins each time a new release is out. Currently, we have version 1.522 running and I'll install the 1.523 on Monday. The problem started to happen something like 4 months ago, but it's hard to say who are the culprits, as I've been upgrading all installed plugins at the same pace... 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
SCM/JIRA link daemon commented on JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/27866d795a20c419556de2fed0bbe98e8af42687 Log: Merge pull request #71 from stephanebruckert/patch-2 JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Compare: https://github.com/jenkinsci/email-ext-plugin/compare/96024dab2ceb...27866d795a20 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-poll-action] (JENKINS-18859) using JENKINS_HOME in certain file build trigger doesn't work
Curtis Wilson
created JENKINS-18859
using JENKINS_HOME in certain file build trigger doesnt work
Issue Type:
Bug
Assignee:
jieryn
Components:
job-poll-action
Created:
19/Jul/13 7:39 PM
Description:
We have one or two jobs using the "Build when certain files are found" build trigger. One of those "certain files" is in a subdirectory of the JENKINS_HOME directory. Currently, it appears that I am not able to use the ${JENKINS_HOME} environment var in the directory field of the build trigger. It throws an error of "Directory not found"
Changing it to a hard-coded path (/var/lib/jenkins for example) works successfully.
Environment:
Jenkins 1.520 - CentOS rpm
Project:
Jenkins
Priority:
Minor
Reporter:
Curtis Wilson
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-poll-action] (JENKINS-18859) using JENKINS_HOME in certain file build trigger doesn't work
jieryn assigned JENKINS-18859 to Unassigned using JENKINS_HOME in certain file build trigger doesnt work Change By: jieryn (19/Jul/13 8:00 PM) Assignee: jieryn 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-18805) Gerrit Triger fails on vote
Patryk Duński commented on JENKINS-18805 Gerrit Triger fails on vote Yes, that's true. This log is not related. But I discovered what is: I'm using Gerrit 2.6.1 and it happens right after init on this version (with default configuration). Voting works fine for Gerrit 2.5.x and 2.6.1 after update from 2.5.x. I'm guessing it's because of changes in labels. 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.
