[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Nickolay Martinov commented on JENKINS-15355 AdjunctManager: exception upon startup Can see the issue in Jenkins ver. 1.505 Mar 15, 2013 7:49:36 AM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping adjunct tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at
[JIRA] [core] (JENKINS-7488) CLONE -java.io.IOException: Unable to delete FOLDER_NAME - files in dir: [WEB_REFERENCE_FILE]
Nickolay Martinov commented on JENKINS-7488 CLONE -java.io.IOException: Unable to delete FOLDER_NAME - files in dir: [WEB_REFERENCE_FILE] I can see a bit different stack trace on Jenkins ver. 1.505 Mar 17, 2013 2:06:39 PM hudson.model.Run execute SEVERE: Failed to save build record java.io.IOException: Unable to delete /home/ci/mst/jobs/Infrastructure_free_space_monitoring/configurations/axis-label/ingot/builds/2013-03-17_14-06-01/build.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:184) at hudson.model.Run.save(Run.java:1702) at hudson.model.Run.execute(Run.java:1623) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Peter Florijn created JENKINS-17488 java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 05/Apr/13 6:44 AM Description: java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Project: Jenkins Priority: Major Reporter: Peter Florijn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rtc] (JENKINS-17489) RTC Plugin - Password are still visible in console output if scm load fails
Phil Rumble created JENKINS-17489 RTC Plugin - Password are still visible in console output if scm load fails Issue Type: Bug Assignee: Deluan Quintão Components: rtc Created: 05/Apr/13 7:25 AM Description: Password are still visible in console output if scm load fails Project: Jenkins Priority: Major Reporter: Phil Rumble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [periodicbackup] (JENKINS-17487) Allow Excludes in Full Backup
Marc Brugger updated JENKINS-17487 Allow Excludes in Full Backup somehow the patch file got lost when creating this issue. Here it is again Change By: Marc Brugger (05/Apr/13 7:41 AM) Attachment: periodicbackup-plugin.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17359) Git plugin: add 'clean before checkout' option
Ferry Huberts updated JENKINS-17359 Git plugin: add clean before checkout option Change By: Ferry Huberts (05/Apr/13 8:36 AM) Summary: Gitplugin: add clean mustbeperformed_before_ before checkout ,notafter option This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17110) Hover-over Build Now broken for parameterized jobs: This page expects a form submission
Joost commented on JENKINS-17110 Hover-over Build Now broken for parameterized jobs: This page expects a form submission This exception is also thrown when clicking the "build now" link on the main job page. It will show the page that lists the job parameters though, after which you can click "build" without any problems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15655) Bad $PATH variable on AIX
Yury Pukhalsky updated JENKINS-15655 Bad $PATH variable on AIX Change By: Yury Pukhalsky (05/Apr/13 9:30 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17490) Maven build step (Default) don't honor PATH
Nicolas De Loof commented on JENKINS-17490 Maven build step (Default) dont honor PATH This is a more generic issue, not limited to maven build task, as Jenkins ProcessLauncher inherits master environment, that overrides the environment set for the build. The later should win when a conflict occurs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15061) Wrong LIBPATH when running ssh slave on AIX
Yury Pukhalsky updated JENKINS-15061 Wrong LIBPATH when running ssh slave on AIX Change By: Yury Pukhalsky (05/Apr/13 9:31 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15107) Cannot parse form data (jenkins asks this to be reported)
Yury Pukhalsky updated JENKINS-15107 Cannot parse form data (jenkins asks this to be reported) Change By: Yury Pukhalsky (05/Apr/13 9:32 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
pedro reis created JENKINS-17491 xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 05/Apr/13 10:45 AM Description: (seems similar to Jenkins bug #11858) Archiving artifacts xUnit INFO - Starting to record. xUnit INFO - Processing CppUnit-1.12.1 (default) xUnit INFO - CppUnit-1.12.1 (default) - 80 test report file(s) were found with the pattern '*/stage/test_results/.xml' relative to 'e:\h\workspace\MXF_SDK\LICENSE\MOG_PAY_VERSION\label\vs90' for the testing framework 'CppUnit-1.12.1 (default)'. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.UnsupportedOperationException: Failed to link the library: interface hudson.util.jna.Kernel32 at hudson.util.jna.InitializationErrorInvocationHandler.invoke(InitializationErrorInvocationHandler.java:28) at $Proxy17.GetFileAttributesW(Unknown Source) at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) at hudson.Util.isSymlink(Util.java:322) at hudson.Util.deleteRecursive(Util.java:283) at hudson.FilePath$11.invoke(FilePath.java:1000) at hudson.FilePath$11.invoke(FilePath.java:997) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(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 hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Library$Handler at com.sun.jna.Native.loadLibrary(Native.java:366) at com.sun.jna.Native.loadLibrary(Native.java:351) at hudson.util.jna.Kernel32Utils.load(Kernel32Utils.java:85) at hudson.util.jna.Kernel32.clinit(Kernel32.java:37) ... 17 more Checking console output Finished: FAILURE Environment: master at Linux; slave vs90 at Windows 7 32bits Project: Jenkins Labels: plugin exception Priority: Major Reporter: pedro reis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-12619) Failed to test the validity of the user name on all security matrices since upgrade
davida2009 commented on JENKINS-12619 Failed to test the validity of the user name on all security matrices since upgrade Hi I am running Jenkins LTS 1.480.3. We have been seeing this error: "Failed to test the validity of the user name x" when 'Project-based Matrix Authorization Strategy' is selected in the Configuration screen. for a long time. Any chance of a fix soon please? David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
davida2009 commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails Still hoping for a fix for this bug. David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
pedro reis commented on JENKINS-17491 xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception . For one of our Jobs to be built, at generatedJUnitFiles\CppUnit there exist the files TEST-1404055753.xml and TEST--2066736517.xml, both with this text inside: ?xml version="1.0" encoding="UTF-8"? testsuite errors="0" failures="1" tests="3" name="cppunit" testcase classname="TestEditorBridge" name="testRunOperation" time="0" failure message="equality assertion failed - Expected: 0 - Actual : -2" type="Assertion"/ system-err File - .\MOG\Operation\EditorBridge\TestEditorBridge.cpp Line - 64 /system-err /testcase testcase classname="TestEditorBridge" name="testInvalidConfigParams" time="0"/ testcase classname="TestEditorBridge" name="testInvalidThumbnail" time="0"/ /testsuite . Also, I've noted that the xunit latest version is 1.53 (on xunit site), and my Jenkins (v1.502) just shows xunit v1.52 as last version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
pedro reis edited a comment on JENKINS-17491 xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception . For one of our Jobs to be built, at generatedJUnitFiles\CppUnit there exist the files TEST-1404055753.xml and TEST--2066736517.xml, both with this text inside: ?xml version="1.0" encoding="UTF-8"? testsuite errors="0" failures="1" tests="3" name="cppunit" testcase classname="TestEditorBridge" name="testRunOperation" time="0" failure message="equality assertion failed - Expected: 0 - Actual : -2" type="Assertion"/ system-err File - .\MOG\Operation\EditorBridge\TestEditorBridge.cpp Line - 64 /system-err /testcase testcase classname="TestEditorBridge" name="testInvalidConfigParams" time="0"/ testcase classname="TestEditorBridge" name="testInvalidThumbnail" time="0"/ /testsuite . Also, I've noted that the xunit latest version is 1.53 (on xunit site), and my Jenkins (v1.502) just shows xunit v1.52 as last version. . The other slaves don't have this problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-16695) clone workspace scm only saves workspace.tar.gz, not workspace.zip
Martin Scherer commented on JENKINS-16695 clone workspace scm only saves workspace.tar.gz, not workspace.zip I tried your patch, but the file name is still "tar.gz". I try to use the clone as SCM on a different node, than it has been created. In the test cases the method string sometimes contains "zip" so we should compare with ignore case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clone-workspace] (JENKINS-15038) Switching archive type of cloned workspace leads to Exception in further jobs
Martin Scherer closed JENKINS-15038 as Duplicate Switching archive type of cloned workspace leads to Exception in further jobs JENKINS-16695 Change By: Martin Scherer (05/Apr/13 12:07 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] [clone-workspace] (JENKINS-15038) Switching archive type of cloned workspace leads to Exception in further jobs
Martin Scherer resolved JENKINS-15038 as Duplicate Switching archive type of cloned workspace leads to Exception in further jobs related to JENKINS-16695 Change By: Martin Scherer (05/Apr/13 12:07 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-11774) Mass-configure triggers in Email-Ext-plugin
Michael Klein updated JENKINS-11774 Mass-configure triggers in Email-Ext-plugin I've extended the Slicer to configure the triggers of the Email-Ext-plugin with version 2.18 or higher. The attached patch file contains the necessary changes on the code. It would be great, if these changes could find the way into the next release of the Slicer. Change By: Michael Klein (05/Apr/13 12:52 PM) Attachment: triggerPatch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xfpanel] (JENKINS-16635) NPE in XFPanel XFPanelEntry.getNumberOfFailedBuilds
Tim Golding commented on JENKINS-16635 NPE in XFPanel XFPanelEntry.getNumberOfFailedBuilds Same issue here: WARNING: Caught exception evaluating: job.numberOfFailedBuilds in /view/Status%20Board/headlessdisplay. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ... Caused by: java.lang.NullPointerException at maps.hudson.plugin.xfpanel.XFPanelView$XFPanelEntry.getNumberOfFailedBuilds(XFPanelView.java:664) Jenkins 1.509 eXtreme Feedback Panel 1.1.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [performance-plugin] (JENKINS-17493) NullPointer Exception when parsing result report
Igor Escobar created JENKINS-17493 NullPointer Exception when parsing result report Issue Type: Bug Affects Versions: current Assignee: Manuel Carrasco Attachments: Screen Shot 2013-04-05 at 10.29.49 AM.png Components: performance-plugin Created: 05/Apr/13 1:45 PM Description: I'm getting error 500 with NullPointerException. The problem occurs when the build finishes and the plugin tries to parse the result, when I click on the performance report link, this is what happens: Status Code: 500 Exception: Stacktrace: java.lang.NullPointerException at hudson.model.Run.getRootDir(Run.java:943) at hudson.plugins.performance.PerformanceReportMap.parseReports(PerformanceReportMap.java:212) at hudson.plugins.performance.PerformanceReportMap.init(PerformanceReportMap.java:56) at hudson.plugins.performance.PerformanceBuildAction.getPerformanceReportMap(PerformanceBuildAction.java:79) at hudson.plugins.performance.PerformanceBuildAction.getTarget(PerformanceBuildAction.java:58) at hudson.plugins.performance.PerformanceBuildAction.getTarget(PerformanceBuildAction.java:15) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:604) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) 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:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at
[JIRA] [core] (JENKINS-16942) hudson.util.SecretRewriterTest test fail on Windows 7
Jesse Glick resolved JENKINS-16942 as Fixed hudson.util.SecretRewriterTest test fail on Windows 7 This was merged but I guess the JIRA commented bot is broken? Change By: Jesse Glick (05/Apr/13 2:20 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] [clone-workspace] (JENKINS-16695) clone workspace scm only saves workspace.tar.gz, not workspace.zip
Pedro Rodriguez commented on JENKINS-16695 clone workspace scm only saves workspace.tar.gz, not workspace.zip There is a pull request for this, so ignore the patch. https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/pull/7 Though it is the same change, so the patch should work. I did not test multiple nodes, but I don't see how that would matter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copyartifact] (JENKINS-17494) Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer
Jason Spangler created JENKINS-17494 Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 05/Apr/13 3:15 PM Description: Copy Artifact fails when trying to copy artifact stored by the ArtifactDeployer plugin, which stored the artifacts on the machine the job ran on (like the slave machine) in a specified directory. Project: Jenkins Priority: Major Reporter: Jason Spangler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactdeployer] (JENKINS-17494) Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer
Jason Spangler updated JENKINS-17494 Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer Change By: Jason Spangler (05/Apr/13 3:16 PM) Component/s: artifactdeployer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [repository] (JENKINS-17495) browse repository feature 404
Chris Cooper created JENKINS-17495 browse repository feature 404 Issue Type: Bug Affects Versions: current Assignee: magnayn Components: repository Created: 05/Apr/13 3:31 PM Description: I am trying to browse the repository from the main "Maven Repository" link on the left hand side and I get a 404 when I click on it. I'm not sure if it is related but sometimes my build doesn't download the latest successful artifacts either even when using the -U option. If there is a log configuration I can create which would provide more help then please let me know. I do have some warnings in the log about old format data Environment: centos 6 x64, tomcat 7, nginx Project: Jenkins Priority: Major Reporter: Chris Cooper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tasks-plugin] (JENKINS-17496) Remove Ant Plugin Dependency
Mathieu Gervais created JENKINS-17496 Remove Ant Plugin Dependency Issue Type: New Feature Affects Versions: current Assignee: Ulli Hafner Components: tasks-plugin Created: 05/Apr/13 3:43 PM Description: Is it possible to remove the dependency on the ant plugin? In our jenkins instances we enforce best practices to ensure the build can also be executed from the cmd line, without jenkins, and the ant plugin breaks that (since it allows developers to specify which version of ant to use in a way that is jenkins specific, and thus needs to be duplicated for the cmd line). Of course, feel free to close as "won't fix" if this is hard to do, but I thought I'd ask just in case the dependency is superfial and can be easily removed (or made optional?!?!) Thanks for considering this. Project: Jenkins Priority: Minor Reporter: Mathieu Gervais This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [log-parser] (JENKINS-9149) Change Log Parser to act as filter on ConsoleStream so that reported results are available during job execution
Andrew Barnish commented on JENKINS-9149 Change Log Parser to act as filter on ConsoleStream so that reported results are available during job execution I guess this might solve the issue where the current log parser crashes the entire Jenkins instance with very large log files (100MB) This seems to be because it loads the entire log into memory which causes java.lang.OutOfMemoryError: Java heap space This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jira] (JENKINS-17498) Make the content of the comment extensible
Kohsuke Kawaguchi created JENKINS-17498 Make the content of the comment extensible Issue Type: New Feature Assignee: Unassigned Components: jira Created: 05/Apr/13 4:05 PM Description: It'd be nice if the JIRA plugin allows some customizability to the content of the comment it posts to JIRA. The abstraction could be as simple as a sequence of JiraCommentContentGenerator or whatever, where we just allow each of them to generate some content and concatenate them together. More sophisicated kind of such JiraCommentContentGenerator could then offer template language capability like email-ext plugin does, but a number of default implementations that do reasonable things would be probably good enough for many. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Bruno P. Kinoshita commented on JENKINS-17215 TAP plugin can prevent Jenkins startup And as this build raised this exception during initialization, Jenkins didn't load it. Thus, I've lost my history too, remaining only 1 build (the one I didn't modify). My guess is that if we manage to fix whatever wrong information we find in build.xml, you'll have your build history back and no more initialization errors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.
Patrick Byrne commented on JENKINS-13865 Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy. Running 1.506 and we are seeing this log file 'decoration' when color xterm output is turned on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [openid] (JENKINS-17499) OpenID plugin is using cryptic URL as the user ID with me.yahoo.com
Kohsuke Kawaguchi created JENKINS-17499 OpenID plugin is using cryptic URL as the user ID with me.yahoo.com Issue Type: Task Assignee: Kohsuke Kawaguchi Components: openid Created: 05/Apr/13 5:03 PM Description: Not sure if this is a bug in the OpenID plugin, but need to verify. The identitiy URL is too lengthy and cryptic to be of a practical use. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Bruno P. Kinoshita commented on JENKINS-17215 TAP plugin can prevent Jenkins startup Created a sample repository 1 at GitHub to isolate the issue. There I used the same xstream library as Jenkins 1.496, as well as same tap4j as TAP Plug-in 1.9 (3.3). Unfortunately (or fortunately) I didn't see the same error. Maybe I'm missing something, so I'll continue to investigate. 1 https://github.com/tupilabs/xstream-sandbox This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [android-emulator] (JENKINS-16392) Hardware properties like hw.ramSize and vm.heapSize should be set in hardware-qemu.ini instead of config.ini for newer Android SDKs
Christopher Orr commented on JENKINS-16392 Hardware properties like hw.ramSize and vm.heapSize should be set in hardware-qemu.ini instead of config.ini for newer Android SDKs Are you sure? I tried changing some settings in each file, and config.ini seemed to be authoritative. Updating the config.ini and starting the emulator seems to overwrite values in hardware-qemu.ini and the emulator starts fine even if I remove hardware-qemu.ini, using the hw.ramSize I set in config.ini. This is with the latest SDK (21.1) and an Android 4.2 emulator. Do you have some documentation or a test case showing that hardware-qemu.ini is the place to change things, and for which platform/tools versions? Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
Christopher Orr closed JENKINS-15537 as Not A Defect Target ABI field doesnt handle Token Expansion Was already fixed before this issue. Change By: Christopher Orr (05/Apr/13 5:10 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.
Jesse Glick resolved JENKINS-13865 as Fixed Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy. Looks like this was fixed long ago. Change By: Jesse Glick (05/Apr/13 5:28 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] [build-flow] (JENKINS-17500) Buildflow build layout is less than optimal
Kohsuke Kawaguchi
created JENKINS-17500
Buildflow build layout is less than optimal
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
05/Apr/13 5:44 PM
Description:
I was trying the following simple DSL and found that the layout was suboptimal:
parallel(
{ build("step1"); },
{ build("step2"); });
[3,4].each { n - build("step${n}") }
There were two issues specifically:
There should be edges from step1 and step2 to step3, but there was only one edge step1 to step3, and no step2 to step3 edge.
Step3 was laid out left of the step1 and step2, whereas I expected the direction of the graph to be preserved.
Project:
Jenkins
Priority:
Major
Reporter:
Kohsuke Kawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Andre Turgeon assigned JENKINS-16617 to Andre Turgeon Github SQS plugin not starting jobs on Jenkins 1.500 Change By: Andre Turgeon (05/Apr/13 6:13 PM) Assignee: AndreTurgeon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Andre Turgeon commented on JENKINS-16617 Github SQS plugin not starting jobs on Jenkins 1.500 A pull request was submitted with a fix for this issue. See: https://github.com/jenkinsci/github-sqs-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson assigned JENKINS-15808 to Francois Valdy CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Francois, Could you attempt to reproduce with a recent version? Thanks, Andy Change By: Andrew Erickson (05/Apr/13 6:17 PM) Assignee: rsandell FrancoisValdy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [plugin] (JENKINS-16669) GitHub SQS Plugin works only once after project config
Andre Turgeon commented on JENKINS-16669 GitHub SQS Plugin works only once after project config A pull request was submitted with a fix for this issue. See: https://github.com/jenkinsci/github-sqs-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-16669) GitHub SQS Plugin works only once after project config
Andre Turgeon resolved JENKINS-16669 as Fixed GitHub SQS Plugin works only once after project config Change By: Andre Turgeon (05/Apr/13 6:20 PM) Status: Open Resolved Assignee: AaronWalker AndreTurgeon 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-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Andre Turgeon resolved JENKINS-16617 as Fixed Github SQS plugin not starting jobs on Jenkins 1.500 Change By: Andre Turgeon (05/Apr/13 6:21 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-17215) TAP plugin can prevent Jenkins startup
Bruno P. Kinoshita commented on JENKINS-17215 TAP plugin can prevent Jenkins startup Alex, could you confirm if the build.xml attached, is the one that is failing, please? I couldn't reproduce the error using your build.xml in my tests (link above). Cheers, B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17215) TAP plugin can prevent Jenkins startup
Bruno P. Kinoshita started work on JENKINS-17215 TAP plugin can prevent Jenkins startup Change By: Bruno P. Kinoshita (05/Apr/13 6:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17501) Repeatable delete button should use the same dotted line to indicate the scope of deletion
Kohsuke Kawaguchi created JENKINS-17501 Repeatable delete button should use the same dotted line to indicate the scope of deletion Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: core Created: 05/Apr/13 6:31 PM Description: In a highly nested configuration UI, the "Delete" button doesn't really tell which section it is removing. To make this obvious, the hover action on the delete button should indicate the scope of the deletion. Project: Jenkins Labels: feedback Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Intermittent timeouts trying to access Jenkins Build Server web interface
We are using Jenkins ver. 1.437 on a linux box and used in conjuction with a mac slave. Our developers are experiencing issues with the web interface of Jenkins timing out intermittently. I am looking at the build server timeout plug in as an option but I do not know if this will resolve the issue or if this is even a good option. Can someone please provide me with some suggestions or potential troubleshooting tactics. Thanks in advance for taking time to read and any suggestions would be greatly appreciated. -- View this message in context: http://jenkins.361315.n4.nabble.com/Intermittent-timeouts-trying-to-access-Jenkins-Build-Server-web-interface-tp4661697.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14067) Polish localization breaks permalink descriptions
dogfood commented on JENKINS-14067 Polish localization breaks permalink descriptions Integrated in jenkins_main_trunk #2435 FIXED JENKINS-14067 Polish localization breaks permalink descriptions (Revision 4c2f865770286e120c3fbc2a470159f5c1346511) Result = SUCCESS github : 4c2f865770286e120c3fbc2a470159f5c1346511 Files : core/src/main/resources/hudson/model/PermalinkProjectAction/Permalink/link_pl.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15365) Invalid translation
dogfood commented on JENKINS-15365 Invalid translation Integrated in jenkins_main_trunk #2435 FIXED JENKINS-15365 Invalid translation (Revision 1565fc7a60f49c09bdf88fd5b2476fcd73f1b4b3) Result = SUCCESS github : 1565fc7a60f49c09bdf88fd5b2476fcd73f1b4b3 Files : core/src/main/resources/hudson/model/AbstractBuild/tasks_pl.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mask-passwords] (JENKINS-17502) Password is not masked if a escaped version is shown in the log
andreasmandel created JENKINS-17502 Password is not masked if a escaped version is shown in the log Issue Type: Improvement Affects Versions: current Assignee: Daniel Petisme Components: mask-passwords Created: 05/Apr/13 8:12 PM Description: If the password contains a character that is printed in a escaped form in the log output, the masking does not work. In my case, I use ant and its echoproperties task. The password "pa##w0rd" will be echoed as "paw0rd" and thus not masked. It would be good to also catch some alternative escaped forms? A different solution could be, to give the opportunity to enter additional patterns that are not set as properties but masked if they appear in the log. Project: Jenkins Priority: Major Reporter: andreasmandel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [htmlpublisher] (JENKINS-14450) Jenkins Job is aborted when job configuration changes
William Lichtenberger updated JENKINS-14450 Jenkins Job is aborted when job configuration changes Change By: William Lichtenberger (05/Apr/13 10:47 PM) Component/s: htmlpublisher 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Fred Beringer commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException I'm running into the same issue with a local install of Jenkins and TestLink. Configuration looks correct on my side: Preparing TestLink client API. Using TestLink URL: http://localhost/testlink/lib/api/xmlrpc.php FATAL: java.util.HashMap cannot be cast to [Ljava.lang.Object; java.lang.ClassCastException: java.util.HashMap cannot be cast to [Ljava.lang.Object; at br.eti.kinoshita.testlinkjavaapi.util.Util.castToArray(Util.java:642) at br.eti.kinoshita.testlinkjavaapi.TestProjectService.getTestProjectByName(TestProjectService.java:111) at br.eti.kinoshita.testlinkjavaapi.TestLinkAPI.getTestProjectByName(TestLinkAPI.java:485) at hudson.plugins.testlink.TestLinkBuilder.getTestLinkSite(TestLinkBuilder.java:246) at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [htmlpublisher] (JENKINS-14450) Jenkins Job is aborted when job configuration changes
William Lichtenberger commented on JENKINS-14450 Jenkins Job is aborted when job configuration changes We've just discovered that this error is actually due to the HTML Publisher plug in. In order to reproduce, create a master / slave job that does anything (to proove this I ran a groovy script that sleeped for 30 seconds). Then have it archive an HTML report when the job is done. After you've done those two steps, now any changes that are made to the jobs configuration will cause the current running jobs to be aborted on the slaves. SLAVE OUTPUT-- Sleeping Sleeping Status Code: 404 Exception: Stacktrace: (none) Generated by Winstone Servlet Engine v0.9.10 at Fri Apr 05 17:45:54 CDT 2013 SLAVE OUTPUT-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-14450) Jenkins Job is aborted when job configuration changes
William Lichtenberger updated JENKINS-14450 Jenkins Job is aborted when job configuration changes Change By: William Lichtenberger (05/Apr/13 10:53 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [htmlpublisher] (JENKINS-14450) Jenkins Job is aborted when job configuration changes
William Lichtenberger commented on JENKINS-14450 Jenkins Job is aborted when job configuration changes Better steps to reproduce: 1) Create a master-slave job that uses the HTML Publisher plugin to archive an html file. (I always select Keep past HTML reports) 2) Start the job. 3) While the job is still running on the slave, modify the configuration of the job (in any way). 4) As soon as you save / apply, the job will be aborted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-12214) Log rotator should be pluggable
Kohsuke Kawaguchi resolved JENKINS-12214 as Fixed Log rotator should be pluggable Implemented as of 1.503. Change By: Kohsuke Kawaguchi (05/Apr/13 11:03 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
Jesse Glick updated JENKINS-8614 ProcessTreeTest fails on Windows Change By: Jesse Glick (05/Apr/13 11:32 PM) URL: https://github.com/jenkinsci/jenkins/pull/752 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-8614) ProcessTreeTest fails on Windows
Jesse Glick started work on JENKINS-8614 ProcessTreeTest fails on Windows Change By: Jesse Glick (05/Apr/13 11:36 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita started work on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Change By: Bruno P. Kinoshita (06/Apr/13 12:43 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hello @Supratim, Sorry for the delay. I've been busy with other project/plug-ins and couldn't find a cycle to work on Jenkins, nor TestLink nor this plug-in. Sorry. Since Wednesday I've been working on all this tools, but first I had to release a 1.9.4 testlink-java-api version. And yesterday another version, now 1.9.5, of the testlink-java-api. Now I'm working on these issues for 1.9.5/1.9.6. Thanks for confirming this issue @Fred. I'll take a look on this. Looks like a simple mismatch between the parameters of the testlink-java-api used by the plug-in, and TestLink. BTW, let me say that today I'm extremely happy, to receive a comment in this plug-in by you. When I wrote this plug-in, the initial version, was highly influenced by your blog entries. I was working on a telecom company, as QA engineer for the first time, and faced the need to integrate my CI jobs with the Test Management team. Not knowing much about test management, your blog was one of the most important resources. So, thank you very much!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jerry Maloney commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Additional commit for the same pull request addresses Jesse's suggestions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Bruno P. Kinoshita commented on JENKINS-17488 java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Hoi Peter I couldn't reproduce this issue. Could you include more information to help me reproduce and fix it, please? Thanks in advance! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Bruno P. Kinoshita started work on JENKINS-17488 java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Change By: Bruno P. Kinoshita (06/Apr/13 2:38 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] [tap] (JENKINS-16674) TAP parser fails parsing output with messages
Bruno P. Kinoshita closed JENKINS-16674 as Wont Fix TAP parser fails parsing output with messages Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3:02 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-16647) parse test duration from TAP file for tapTestReport pages
Bruno P. Kinoshita closed JENKINS-16647 as Fixed parse test duration from TAP file for tapTestReport pages Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita closed JENKINS-15322 as Fixed NOTESTS in TAP response gives parse error and stack trace from plugin Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-17135) TAP should display test name/description if available
Bruno P. Kinoshita closed JENKINS-17135 as Fixed TAP should display test name/description if available Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-16325) TAP Parser can't handle the output from prove
Bruno P. Kinoshita closed JENKINS-16325 as Not A Defect TAP Parser cant handle the output from prove Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita closed JENKINS-16326 as Not A Defect TAP Parser cant handle SKIP_ALL Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-17245) Tap plug-in is not listing skipped tests (due to a parser error in tap4j).
Bruno P. Kinoshita closed JENKINS-17245 as Fixed Tap plug-in is not listing skipped tests (due to a parser error in tap4j). Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
Bruno P. Kinoshita closed JENKINS-16971 as Fixed TAP Plug-in not showing TAP contents if it resides in a subdirectory Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-16964) TAP Plug-in does not fail builds with old reports
Bruno P. Kinoshita closed JENKINS-16964 as Fixed TAP Plug-in does not fail builds with old reports Fixed in 1.10 Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [tap] (JENKINS-17136) TAP testReport not listing failing tests for configurations
Bruno P. Kinoshita commented on JENKINS-17136 TAP testReport not listing failing tests for configurations 1.10 released. Will try to include this issue in 1.11, to be released in the next days (release early, release often This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-15588) TestLink is not getting Updated
Bruno P. Kinoshita commented on JENKINS-15588 TestLink is not getting Updated Ping This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Bruno P. Kinoshita commented on JENKINS-8636 TestLink Plugin FATAL: Error creating test project @Ruslan, @Fran, I'm filtering the issues to cut a new release. This issue already happened twice in the past. One occurrence of this issue is registered here. The other one may be registered here too, under other issue, or maybe in testlink-java-api issues or in my private e-mail inbox. But in both cases, I remember well that it wasn't caused by any bug in neither Jenkins TestLink Plug-in nor in testlink-java-api. Once it was a wrong URL, and the other time we set up a VPS with TestLink. The reporter pointed his Jenkins to this server and successfully downloaded and executed tests using the plug-in. This way, we could isolate the problem, making sure it was either in TestLink or in the web server. Basically, this issue is caused when the XML-RPC client asks for a XML response from a server, but it gets something that is not a valid XML or any stream of data with extra characters (even if not visible - i.e. can't be decoded in console/editor) before the XML content. There's not much I can do to help in this case. If you guys could intercept the communication (using QDPF, Wireshark, etc) between the client and server, perhaps we can analyse what's happening. But besides that, there's not much I can do in the code to help you guys. Sorry :/ Cheers, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17146) Test link plugin is not looking trough my suite name options in testNG
Bruno P. Kinoshita started work on JENKINS-17146 Test link plugin is not looking trough my suite name options in testNG Change By: Bruno P. Kinoshita (06/Apr/13 3:31 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] [testlink] (JENKINS-17147) The configuration for testng method name and data provider is not saved
Bruno P. Kinoshita started work on JENKINS-17147 The configuration for testng method name and data provider is not saved Change By: Bruno P. Kinoshita (06/Apr/13 3:32 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] [testlink] (JENKINS-17146) Test link plugin is not looking trough my suite name options in testNG
Bruno P. Kinoshita commented on JENKINS-17146 Test link plugin is not looking trough my suite name options in testNG Hi @Paul, can you attach a sample XML with your multiple suites, please? I'll run it through testng-parser 1 and will try to fix the issue in the plug-in. Thanks in advance. 1 http://search.maven.org/#artifactdetails%7Ccom.tupilabs%7Ctestng-parser%7C0.1%7Cjar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita started work on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Change By: Bruno P. Kinoshita (06/Apr/13 3:35 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Hi @Jeff, Can you confirm if your TestLink execution statuses have been customized? The plug-in works with the default statuses from TestLink (p = passed). The message returned from the server indicates that either the 'p' status is not available or was changes, or that there's something reaaally out of the way in the plug-in or in one of its libraries Thanks! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-16698) immediately update and show the result of one test case when it completed
Bruno P. Kinoshita commented on JENKINS-16698 immediately update and show the result of one test case when it completed Hi @Yinghua, First of all, thanks for investigating further this issue, and reading about Jenkins API. I have to admit that I never used TransientBuildActionFactory and can't guess what it does by its name. I'll have to read the javadocs, probably the source code + tests to finally (and hopefully) grok it. I'll try to learn about it this weekend and will comment here. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-16698) immediately update and show the result of one test case when it completed
Bruno P. Kinoshita started work on JENKINS-16698 immediately update and show the result of one test case when it completed Change By: Bruno P. Kinoshita (06/Apr/13 3:37 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] [testlink] (JENKINS-16640) Mark in Jenkins build with NOT RUN Test Cases and display in the UI (with colours, etc)
Bruno P. Kinoshita commented on JENKINS-16640 Mark in Jenkins build with NOT RUN Test Cases and display in the UI (with colours, etc) From your description it does make sense. Will try to implement it to see if there's no reason for not doing this way. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-16640) Mark in Jenkins build with NOT RUN Test Cases and display in the UI (with colours, etc)
Bruno P. Kinoshita started work on JENKINS-16640 Mark in Jenkins build with NOT RUN Test Cases and display in the UI (with colours, etc) Change By: Bruno P. Kinoshita (06/Apr/13 3:39 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] [testlink] (JENKINS-16577) TestLink plugin Result Seeker
Bruno P. Kinoshita commented on JENKINS-16577 TestLink plugin Result Seeker Not yet. We'll have to create a new result seeker for this. Can't promise I'll finish it by this weekend, but hopefully will code this new result seeker in the next days Thanks for reporting! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-16118) Testlink Plug-In: get Custom field information for Testplans and Testsuites
Bruno P. Kinoshita commented on JENKINS-16118 Testlink Plug-In: get Custom field information for Testplans and Testsuites Hi Cedric, Looks to me like you are using a custom field which scope is Test Suites (or something similar, but not Test Cases in design scope). You have to use the right custom field type in order to use these custom fields in your automated test case in Jenkins. Does it help? Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-16118) Testlink Plug-In: get Custom field information for Testplans and Testsuites
Bruno P. Kinoshita resolved JENKINS-16118 as Not A Defect Testlink Plug-In: get Custom field information for Testplans and Testsuites Marking as "Not A Defect" in order to organize my work and cut a new release. Feel free to change its status, or just comment your answer and I'll try to change to the right status. Thanks! Change By: Bruno P. Kinoshita (06/Apr/13 3:43 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-15937) TestLink Plugin prevents Jenkins from parsing Jobs
Bruno P. Kinoshita started work on JENKINS-15937 TestLink Plugin prevents Jenkins from parsing Jobs Change By: Bruno P. Kinoshita (06/Apr/13 3: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] [testlink] (JENKINS-15937) TestLink Plugin prevents Jenkins from parsing Jobs
Bruno P. Kinoshita commented on JENKINS-15937 TestLink Plugin prevents Jenkins from parsing Jobs Hi Martin, Thanks for reporting. Could you attach your build.xml that is failing please? In case there's any sensitive information (user id, url's, etc) please replace it by anything, but don't change the line position (it may be useful for finding the root cause of the problem). Thanks! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Bruno P. Kinoshita updated JENKINS-17023 Jenkins Testlink plugin Found 0 test result is show while test is runned Change By: Bruno P. Kinoshita (06/Apr/13 3:49 AM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Bruno P. Kinoshita started work on JENKINS-17023 Jenkins Testlink plugin Found 0 test result is show while test is runned Change By: Bruno P. Kinoshita (06/Apr/13 3:52 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] [testlink] (JENKINS-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Bruno P. Kinoshita
commented on JENKINS-17023
Jenkins Testlink plugin Found 0 test result is show while test is runned
Hi @Abdallah,
Thanks for reporting and including sufficient information to investigate the issue (regarding the book.pdf, you could have included only the link, that's all right, but the Jira infra team will have to remove it later :=)
My guess is that your test cases in TestLink are not marked as Automated. Your console output has the following output message:
"Found 0 automated test cases in TestLink."
It means that the plug-in tried (using testlink-java-api) to retrieve the test cases from TestLink that are marked as Automated, and associated to the test plan used in the job configuration ("My first test plan ?).
Does that help?
Thanks! Bruno
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [testlink] (JENKINS-16698) immediately update and show the result of one test case when it completed
Bruno P. Kinoshita updated JENKINS-16698 immediately update and show the result of one test case when it completed Change By: Bruno P. Kinoshita (06/Apr/13 3:59 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17147) The configuration for testng method name and data provider is not saved
Bruno P. Kinoshita updated JENKINS-17147 The configuration for testng method name and data provider is not saved Change By: Bruno P. Kinoshita (06/Apr/13 4:02 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita updated JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Change By: Bruno P. Kinoshita (06/Apr/13 4:02 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17451) projects tied to slave shows unrelated maven module jobs
sogabe assigned JENKINS-17451 to sogabe projects tied to slave shows unrelated maven module jobs Change By: sogabe (06/Apr/13 4:11 AM) Assignee: sogabe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita edited a comment on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Bug confirmed when using the plug-in with TestLlink 1.9.6. Apparently, TestLink XML-RPC method getTestProjectByName, which used to return an array, is now returning a map. Please see 1 to track the changes, but probably tomorrow (Saturday) it will be fixed in trunk, and a release is to be cut in the next days. Thanks! 1 https://github.com/kinow/testlink-java-api/issues/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Bug confirmed when using the plug-in with TestLlink 1.9.6. Apparently, TestLink XML-RPC method getTestProjectByName, which used to return an array, is now returning a map. Please see 1 to track the changes, but probably tomorrow (Saturday) it will be fixed in trunk, and a release is to be cut in the next days. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) projects tied to slave shows unrelated maven module jobs
dogfood commented on JENKINS-17451 projects tied to slave shows unrelated maven module jobs Integrated in jenkins_main_trunk #2436 FIXED JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only. (Revision 3a6de84f6746d54dd0f3048312db067c835ee727) Result = SUCCESS Seiji Sogabe : 3a6de84f6746d54dd0f3048312db067c835ee727 Files : changelog.html core/src/main/java/hudson/model/Label.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
