[JIRA] (JENKINS-17303) Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin
Ross Rowe resolved JENKINS-17303 as Fixed Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin Hi, sorry about that, I've released version 1.51 which should resolve the issue, can you let me know if you have any further issues? Cheers, Ross Change By: Ross Rowe (01/Apr/13 7:39 AM) Status: In Progress 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] (JENKINS-16540) NPE when Job finishes after taking Slave offline
stevengbrown assigned JENKINS-16540 to stevengbrown NPE when Job finishes after taking Slave offline Change By: stevengbrown (01/Apr/13 10:21 AM) Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16540) NPE when Job finishes after taking Slave offline
stevengbrown resolved JENKINS-16540 as Duplicate NPE when Job finishes after taking Slave offline Resolved as a duplicate of JENKINS-16778. Change By: stevengbrown (01/Apr/13 10:23 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16540) NPE when Job finishes after taking Slave offline
stevengbrown closed JENKINS-16540 as Duplicate NPE when Job finishes after taking Slave offline Change By: stevengbrown (01/Apr/13 10:24 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] (JENKINS-16598) Timestamper: javascript error in IE8
stevengbrown commented on JENKINS-16598 Timestamper: _javascript_ error in IE8 Fix included in Timestamper 1.5.2 release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
stevengbrown commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Fix included in Timestamper 1.5.3 release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7112) Allow plugins to transform the BuildListener log output.
stevengbrown closed JENKINS-7112 as Fixed Allow plugins to transform the BuildListener log output. Change By: stevengbrown (01/Apr/13 10:28 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] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
stevengbrown updated JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Change By: stevengbrown (01/Apr/13 10:31 AM) Component/s: timestamper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12248) Concatenate changelogs from prior failed builds
Jai Govindani commented on JENKINS-12248 Concatenate changelogs from prior failed builds Hi everyone. I need this bug/feature so much that I'm willing to pay 100.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/224/concatenate-changelogs-from-prior-failed-builds). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11362) Strange delay during a maven job build
Jesse Glick commented on JENKINS-11362 Strange delay during a maven job build Note: 3.1.0-alpha-1 with this fix has been proposed. Looks like it will take close to a year to get this simple fix into an official release, sigh. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17421) Add support for Build Blocker plugin
Omair Inam updated JENKINS-17421 Add support for Build Blocker plugin Change By: Omair Inam (01/Apr/13 12:55 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17421) Add support for Build Blocker plugin
Omair Inam created JENKINS-17421 Add support for Build Blocker plugin Issue Type: Bug Assignee: mdonohue Components: configurationslicing Created: 01/Apr/13 12:55 PM Description: https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin Project: Jenkins Priority: Major Reporter: Omair Inam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17422) Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter
Jesper Jensen created JENKINS-17422 Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 01/Apr/13 2:07 PM Description: INFO: Loading configuration... Apr 01, 2013 9:22:44 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin dynamicparameter java.io.IOException: Dependency scriptler (2.2) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479) at hudson.PluginManager$2$1$1.run(PluginManager.java:332) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Environment: Windows 2008 R2 java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) Client VM (build 23.7-b01, mixed mode, sharing) Project: Jenkins Priority: Major Reporter: Jesper Jensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17423) Exception on start up: SEVERE: An exception occurred during processing of the org.apache.wink.server.internal.providers.entity.html.HtmlProvider class. This class is ignored.
Jesper Jensen created JENKINS-17423 Exception on start up: SEVERE: An exception occurred during processing of the org.apache.wink.server.internal.providers.entity.html.HtmlProvider class. This class is ignored. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 01/Apr/13 2:09 PM Description: SEVERE: An exception occurred during processing of the org.apache.wink.server.internal.providers.entity.html.HtmlProvider class. This class is ignored. java.lang.IllegalStateException at org.apache.wink.server.internal.contexts.HttpServletRequestWrapperImpl.getCorrectRequest(HttpServletRequestWrapperImpl.java:52) at org.apache.wink.server.internal.contexts.HttpServletRequestWrapperImpl.setRequest(HttpServletRequestWrapperImpl.java:65) at javax.servlet.ServletRequestWrapper.(ServletRequestWrapper.java:25) at javax.servlet.http.HttpServletRequestWrapper.(HttpServletRequestWrapper.java:22) at org.apache.wink.server.internal.contexts.HttpServletRequestWrapperImpl.(HttpServletRequestWrapperImpl.java:74) at org.apache.wink.server.internal.registry.ServletContextAccessor.getContextFromAccessor(ServletContextAccessor.java:67) at org.apache.wink.common.internal.registry.ContextAccessor.getContext(ContextAccessor.java:48) at org.apache.wink.server.internal.registry.ServerInjectableFactory$ServerContextParam.getValue(ServerInjectableFactory.java:157) at org.apache.wink.common.internal.lifecycle.CreationUtils.injectFields(CreationUtils.java:92) at org.apache.wink.common.internal.lifecycle.CreationUtils.createObject(CreationUtils.java:67) at org.apache.wink.common.internal.lifecycle.LifecycleManagerUtils.createSingletonObjectFactory(LifecycleManagerUtils.java:61) at org.apache.wink.common.internal.lifecycle.DefaultLifecycleManager.createObjectFactory(DefaultLifecycleManager.java:86) at org.apache.wink.common.internal.lifecycle.LifecycleManagersRegistry.getObjectFactory(LifecycleManagersRegistry.java:85) at org.apache.wink.common.internal.registry.ProvidersRegistry.addProvider(ProvidersRegistry.java:110) at org.apache.wink.server.internal.application.ApplicationProcessor.processClasses(ApplicationProcessor.java:178) at org.apache.wink.server.internal.application.ApplicationProcessor.process(ApplicationProcessor.java:86) at org.apache.wink.server.internal.DeploymentConfiguration.addApplication(DeploymentConfiguration.java:339) at org.apache.wink.server.internal.RequestProcessor.registerDefaultApplication(RequestProcessor.java:99) at org.apache.wink.server.internal.RequestProcessor.(RequestProcessor.java:81) at org.apache.wink.server.internal.servlet.RestServlet.createRequestProcessor(RestServlet.java:152) at org.apache.wink.server.internal.servlet.RestServlet.init(RestServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:39) at com.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.init(HudsonAPIV2ServletFilter.java:66) at hudson.util.PluginServletFilter.addFilter(PluginServletFilter.java:74) at com.marvelution.hudson.plugins.apiv2.APIv2Plugin.start(APIv2Plugin.java:94) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) at hudson.PluginManager$2$1$1.run(PluginManager.java:333) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Environment: Windows 2008 R2 java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) Cli
[JIRA] (JENKINS-17424) SEVERE: Failed Loading plugin nodeofflinenotification and SEVERE: Failed Loading plugin pathignore
Jesper Jensen created JENKINS-17424 SEVERE: Failed Loading plugin nodeofflinenotification and SEVERE: Failed Loading plugin pathignore Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 01/Apr/13 2:12 PM Description: Apr 01, 2013 9:28:10 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin nodeofflinenotification hudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371) at hudson.PluginManager$2$1$1.run(PluginManager.java:333) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: org.jruby.exceptions.RaiseException: (LoadError) library `fiber' could not be loaded: java.lang.ClassNotFoundException: org.jruby.ext.fiber.ThreadFiberLibrary Looks like that jruby version included is too old. Environment: Windows 2008 R2 java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) Client VM (build 23.7-b01, mixed mode, sharing) Project: Jenkins Priority: Major Reporter: Jesper Jensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-2374) Master-Slave Workspace Directory Structure Different
Manuel de la Peña commented on JENKINS-2374 Master-Slave Workspace Directory Structure Different Is anybody working on this? I believe that builds folder should not be shared between builds, and it should be consider a bug, as master's folder structure is not been replicated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17425) WARNING: "Failed to scout hudson.security.PAMSecurityRealm" and "Failed to scout hudson.model.ExternalJob"
Jesper Jensen created JENKINS-17425 WARNING: "Failed to scout hudson.security.PAMSecurityRealm" and "Failed to scout hudson.model.ExternalJob" Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Apr/13 2:17 PM Description: INFO: Prepared all plugins Apr 01, 2013 9:30:04 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.security.PAMSecurityRealm java.lang.InstantiationException: file:/C:/Jenkins/plugins/pam-auth/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.security.PAMSecurityRealm at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:312) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1175) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:99) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:352) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.ClassNotFoundException: hudson.security.PAMSecurityRealm at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:942) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 21 more Apr 01, 2013 9:30:04 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.model.ExternalJob java.lang.InstantiationException: file:/C:/Jenkins/plugins/external-monitor-job/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.model.ExternalJob at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:312) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1175) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:99) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:352) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at
[JIRA] (JENKINS-17426) I get a lot of those WARNING: Skipping a non-existent field onlyCopyClaimOnSimilarError
Jesper Jensen created JENKINS-17426 I get a lot of those WARNING: Skipping a non-existent field onlyCopyClaimOnSimilarError Issue Type: Bug Assignee: Unassigned Attachments: jenkins.err.log Components: core Created: 01/Apr/13 2:22 PM Description: See log file. Environment: Windows 2008 R2 java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) Client VM (build 23.7-b01, mixed mode, sharing) Project: Jenkins Priority: Minor Reporter: Jesper Jensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17383) CVS plugin detect changes in 'rlog' but not in 'update'
Isaac Cruz commented on JENKINS-17383 CVS plugin detect changes in 'rlog' but not in 'update' Update: it seems to NOT be related to the date in -D option, I've changed the configuration to download a tag instead of HEAD (leaving the field empty so it actually use HEAD), and it still does not update to the last revision. This is the command displayed in log: cvs update -C -d -P -r HEAD cvs-test It eventually downloads the last revision... but not at least after 1 hour This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17427) sloccount NPE
Shadow Fen created JENKINS-17427 sloccount NPE Issue Type: Bug Assignee: npiguet Components: sloccount Created: 01/Apr/13 3:37 PM Description: sloccount 1.8 running on the master works just fine. sloccount 1.8 is returning NPE when running the same job on a slave: 00:00:00.000 Started by user Dolores Scott 00:00:00.017 [EnvInject] - Loading node environment variables. 00:00:00.164 Building remotely on Dev32_Server in workspace /opt/jenkins-slave/workspace/test-aiken32-compileall 00:00:00.165 00:00:00.165 Deleting project workspace... 00:00:00.959 done 00:00:00.959 00:00:01.017 Checkout:test-aiken32-compileall / /opt/jenkins-slave/workspace/test-aiken32-compileall - hudson.remoting.Channel@1d48c:Dev32_Server 00:00:01.017 Using strategy: Default 00:00:01.063 Last Built Revision: Revision a071cc670b36cd96002feada0f426b13b74d7996 (origin/aiken) 00:00:03.785 Cloning the remote Git repository 00:00:03.790 Cloning repository ssh://aplcm@10.1.1.47/var/git/Integration/appliance.git 00:00:03.875 git --version 00:00:03.876 git version 1.8.0 00:00:26.680 Fetching upstream changes from origin 00:00:27.192 Commencing build of Revision a071cc670b36cd96002feada0f426b13b74d7996 (origin/aiken) 00:00:27.548 Checking out Revision a071cc670b36cd96002feada0f426b13b74d7996 (origin/aiken) 00:00:31.840 [test-aiken32-compileall] $ /bin/sh -xe /tmp/hudson8520274860963285058.sh 00:00:31.873 + cd build 00:00:32.147 [test-aiken32-compileall] $ /bin/sh -xe /tmp/hudson1653286013608686853.sh 00:00:32.205 + sloccount --wide --details . 00:01:09.222 [WARNINGS] Parsing warnings in console log with parser GNU Make + GNU Compiler (gcc) 00:01:18.165 [TASKS] Scanning folder '/opt/jenkins-slave/workspace/test-aiken32-compileall' for files matching the pattern '*/.c,*/.cxx,*/.h,*/.mk,*/Makefile,/.sh' - excludes: 00:01:18.166 [TASKS] Found 2860 files to scan for tasks 00:01:18.166 [TASKS] Found 992 open tasks. 00:01:19.234 [TASKS] Computing warning deltas based on reference build #10 00:01:22.105 ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to exception 00:01:22.105 java.lang.NullPointerException 00:01:22.106 at java.lang.String.lastIndexOf(String.java:1823) 00:01:22.106 at java.lang.String.lastIndexOf(String.java:1805) 00:01:22.106 at hudson.plugins.sloccount.model.SloccountReport.extractFolder(SloccountReport.java:68) 00:01:22.106 at hudson.plugins.sloccount.model.SloccountReport.add(SloccountReport.java:47) 00:01:22.106 at hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:92) 00:01:22.106 at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:59) 00:01:22.107 at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:50) 00:01:22.107 at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:40) 00:01:22.107 at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17) 00:01:22.107 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) 00:01:22.107 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 00:01:22.107 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 00:01:22.107 at hudson.remoting.Request$2.run(Request.java:326) 00:01:22.108 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 00:01:22.108 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 00:01:22.108 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 00:01:22.108 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 00:01:22.108 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 00:01:22.108 at java.lang.Thread.run(Thread.java:619) 00:01:22.233 Sending e-mails to: dolores.sc...@securelogix.com 00:01:22.297 Finished: FAILURE When I revert back to sloccount 1.7 and run the same job on the slave, it works just fine. Environment: CentOS 6.3-64 bit/CentOS 5.6-32bit
[JIRA] (JENKINS-17428) Jenkins v1.508 fails to load build history from disk
Paul Dunham created JENKINS-17428 Jenkins v1.508 fails to load build history from disk Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: build.xml Components: core Created: 01/Apr/13 4:24 PM Description: When Jenkins tries to load the history, I get the following errors in the Jenkins log. This error is repeated for every build number. Note that .../jenkin_builds/111 is a link that points to jenkin_builds/2013-03-31_05-45-11/ the build.xml file in that directory is attached. Apr 1, 2013 9:20:52 AM hudson.model.RunMap retrieve WARNING: could not load /apps/Oracle/Middleware/user_projects/domains/eja_domain/jenkin_builds/111 hudson.util.IOException2: Unable to read /apps/Oracle/Middleware/user_projects/domains/eja_domain/jenkin_builds/2013-03-31_05-45-11/build.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.model.Run.reload(Run.java:311) at hudson.model.Run.(Run.java:297) at hudson.model.AbstractBuild.(AbstractBuild.java:169) at hudson.model.Build.(Build.java:104) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:42) at sun.reflect.GeneratedConstructorAccessor140.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:369) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1054) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:140) at hudson.model.Job.getLastFailedBuild(Job.java:853) at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:93) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:106) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:82) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:162) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at
[JIRA] (JENKINS-17429|[ProjectComponentImpl { name='core', description='Jenkins core', lead='', assigneeType='0', projectId='10172', id='15593' }][0].name) Testing the new subject field
Kohsuke Kawaguchi created JENKINS-17429 Testing the new subject field Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core Created: 01/Apr/13 4:54 PM Description: This is a test. Please disregard. 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] (JENKINS-17429) Testing the new subject field
Kohsuke Kawaguchi commented on JENKINS-17429 Testing the new subject field Please disregard. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17429|core) Testing the new subject field
Kohsuke Kawaguchi updated JENKINS-17429 Testing the new subject field Change By: Kohsuke Kawaguchi (01/Apr/13 5:08 PM) Priority: Major Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17430|core) Manual upload of the plugin needs to look into the plugin manifest
Kohsuke Kawaguchi created JENKINS-17430 Manual upload of the plugin needs to look into the plugin manifest Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Apr/13 5:10 PM Description: When a plugin is manually uploaded, its manifest should be looked at and the file be created/updated under its proper name. A common failure mode is that someone downloads a plugin and the browser names it like "foobar(2).jpi", which ends up getting deployed as a separate plugin. 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] (JENKINS-16646) Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag.
Vladimir Kravets commented on JENKINS-16646 Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag. From our point of view in continous process it's can be life, since there can be exists some issues due which tests are failed (bug or bugs about which we are know) and QA should get build with some limitation.(Since another features are working and QA should test it) To fix these issues need some time e.g. 2-4 days. As I said before QA should get build during this 2-4 days. We are using tagging to have stable(or unstable) build (but not failed). Continous build marks in source control tag e.g. "stable" and nighly build use this tag to have "good" build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16646) Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag.
Vladimir Kravets commented on JENKINS-16646 Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag. Possible fix was implemented in the pull request - https://github.com/jenkinsci/git-plugin/pull/128 Kutzi comments some things in this pull request. Thus I will change some behavior in the fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-5698) Show test-result directly from reportng/testng generated html
Khalith Basha commented on JENKINS-5698 Show test-result directly from reportng/testng generated html I would like to knw tat plugin name>>?? can u please say ASAP This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15248) Auto update violations unstable and heathly limits following a healthy build
Tobias Baum commented on JENKINS-15248 Auto update violations unstable and heathly limits following a healthy build Just in case anyone searches for this term: This behaviour is often called ratcheting. And the corresponding ticket for the coverage plugin is JENKINS-8326. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15248) Auto update violations unstable and heathly limits following a healthy build
Tobias Baum commented on JENKINS-15248 Auto update violations unstable and heathly limits following a healthy build I tried implementing this feature, but I had a lot of problems getting the test infrastructure up and running. Therefore, I commited the changes untested (https://github.com/tobiasbaum/violations-plugin/commits/master). Perhaps someone else with better Jenkins knowledge can ensure that it works (I added everything that seemed necessary to me, but I'm a total newbie) or I will continue when I'm a bit less frustrated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14089) JUnit report - Quarantine intermittent tests
samuel nobs started work on JENKINS-14089 JUnit report - Quarantine intermittent tests Change By: samuel nobs (01/Apr/13 7:16 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14089) JUnit report - Quarantine intermittent tests
samuel nobs assigned JENKINS-14089 to samuel nobs JUnit report - Quarantine intermittent tests Change By: samuel nobs (01/Apr/13 7:16 PM) Assignee: samuel nobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14089) JUnit report - Quarantine intermittent tests
samuel nobs commented on JENKINS-14089 JUnit report - Quarantine intermittent tests i have started looking into doing this. it will receive background task priority and hence go very slowly, so if anyone wanted to speed things up talk to me and we can reassign This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
kutzi resolved JENKINS-13055 as Cannot Reproduce checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed Change By: kutzi (01/Apr/13 7:53 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11721) MavenTestDataPublisher does not work with modules and after restart
kutzi resolved JENKINS-11721 as Incomplete MavenTestDataPublisher does not work with modules and after restart No response from reporter -> closing as Incomplete Change By: kutzi (01/Apr/13 7:54 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3954) OutOfMemoryError on Maven site on SECOND build
kutzi resolved JENKINS-3954 as Incomplete OutOfMemoryError on Maven site on SECOND build No response from reporter -> closing as Incomplete Change By: kutzi (01/Apr/13 7:55 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7970) If all JUnit tests are skipped, the build fails
Todd Edwards commented on JENKINS-7970 If all JUnit tests are skipped, the build fails I would also like to see this patch merged. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17431|subversion) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn created JENKINS-17431 500 Internal Server Error on attempt to run a build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 01/Apr/13 8:47 PM Description: jenkins throws : ERROR: Failed to update https://XXX org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/playspan/!svn/vcc/default': 500 Internal Server Error on attempt to run build. on svn server side in the error log: " Could not access revision times. 500, #0" I think what happened was: when build is requested, svnkit is trying to run svn log on the svn server by runnint it between two time stamps - previous build and current time. sometimes either dates were not recorded on svn server or the current dated obtained on the jenkins server is running ahead of svn server and, I think, this causes the problem. my suggestion: do not use timestamp at all instead run log (or svn diff) between two revision numbers, which are always present on svn server. 2. I think running svn log on remote svn server is not very efficient. I think, would be better: 1. when build is requested, capture current revision on the working space. 2. run svn update 3. capture the revision 4. run log or diff locally between two revisions. this way, jenkins will communicate to svn server just once instead of multiple times. Environment: linux redhat 2.6.18-238.el5 Project: Jenkins Priority: Blocker Reporter: Slava Maslenitsyn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16720) Android SDK installation fails
Steven Luplow commented on JENKINS-16720 Android SDK installation fails I was trying to update to the latest tools version so I could then run API 17 on Jekins. I experienced the same issue. Our set up is - OpenIndiana master, with a Linux slave where the sdk lives. Here is our log message: [android] No Android SDK found; let's install it automatically... Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r21.0.1-linux.tgz [android] Base SDK installed successfully [android] Going to install required Android SDK components... [android] Installing the 'platform-tool,tool' SDK component(s)... $ /home/jenkins/tools/android-sdk/tools/android update sdk -u -o -t platform-tool,tool Error: Flag '-o' is not valid for 'update sdk'. Usage: android [global options] update sdk [action options] Global options: -h --help : Help on a specific command. -v --verbose: Verbose mode, shows errors, warnings and all messages. --clear-cache: Clear the SDK Manager repository manifest cache. -s --silent : Silent mode, shows errors only. Action "update sdk": Updates the SDK by suggesting new platforms to install if available. Options: --proxy-port: HTTP/HTTPS proxy port (overrides settings if defined) --proxy-host: HTTP/HTTPS proxy host (overrides settings if defined) -s --no-https : Uses HTTP instead of HTTPS (the default) for downloads. -a --all : Includes all packages (such as obsolete and non-dependent ones.) -f --force : Forces replacement of a package or its parts, even if something has been modified. -u --no-ui : Updates from command-line (does not display the GUI) -p --obsolete : Deprecated. Please use --all instead. -t --filter: A filter that limits the update to the specified types of packages in the form of a comma-separated list of [platform, system-image, tool, platform-tool, doc, sample, source]. This also accepts the identifiers returned by 'list sdk --extended'. -n --dry-mode : Simulates the update but does not download or install anything. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.plugins.android_emulator.util.Utils.getToolCommand(Utils.java:369) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:413) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:406) at hudson.plugins.android_emulator.SdkInstaller.isPlatformInstalled(SdkInstaller.java:258) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:205) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:190) at hudson.plugins.android_emulator.SdkInstaller.installDependencies(SdkInstaller.java:177) at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:250) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:600) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) project=hudson.maven.MavenModuleSet@1a42f7f[absio-android-IT-4.2] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at hudson.plugins.android_emulator.util.Utils.getToolCommand(Utils.java:369) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:413) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:406) at hudson.plugins.android_emulator.SdkInstaller.isPlatformInstalled(SdkInstaller.java:258) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:205) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:190) at hudson.plugins.android_emulator.SdkInstaller.installDependencies(SdkInstaller.java:177) at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:250) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:600) at hudson.model.AbstractBuild$AbstractBuildExecution.run(Abs
[JIRA] (JENKINS-17432|build-flow) Support FileParameter in build flow plugin
Emil Sit created JENKINS-17432 Support FileParameter in build flow plugin Issue Type: New Feature Assignee: Nicolas De Loof Components: build-flow Created: 01/Apr/13 9:08 PM Description: We use File parameters to enable a sandbox/try build (inspired by http://codeascraft.etsy.com/2011/10/11/did-you-try-it-before-you-committed/). I'd like to use the build flow plugin to kick off a series of downstream builds for testing purposes. As far as I can tell, the plugin does not currently support File parameters because they are not Simple. It'd be useful for this support to be added. Project: Jenkins Priority: Major Reporter: Emil Sit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16720) Android SDK installation fails
Steven Luplow edited a comment on JENKINS-16720 Android SDK installation fails I was trying to update to the latest tools version so I could then run API 17 on Jekins. I experienced the same issue. Our set up is - jenkins runs on top of a OpenIndiana host, over SSH it connects to a Linux slave. The Linux slave is where the SDK and all the installed tools live.. Here is our log message: [android] No Android SDK found; let's install it automatically... Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r21.0.1-linux.tgz [android] Base SDK installed successfully [android] Going to install required Android SDK components... [android] Installing the 'platform-tool,tool' SDK component(s)... $ /home/jenkins/tools/android-sdk/tools/android update sdk -u -o -t platform-tool,tool Error: Flag '-o' is not valid for 'update sdk'. Usage: android [global options] update sdk [action options] Global options: -h --help : Help on a specific command. -v --verbose: Verbose mode, shows errors, warnings and all messages. --clear-cache: Clear the SDK Manager repository manifest cache. -s --silent : Silent mode, shows errors only. Action "update sdk": Updates the SDK by suggesting new platforms to install if available. Options: --proxy-port: HTTP/HTTPS proxy port (overrides settings if defined) --proxy-host: HTTP/HTTPS proxy host (overrides settings if defined) -s --no-https : Uses HTTP instead of HTTPS (the default) for downloads. -a --all : Includes all packages (such as obsolete and non-dependent ones.) -f --force : Forces replacement of a package or its parts, even if something has been modified. -u --no-ui : Updates from command-line (does not display the GUI) -p --obsolete : Deprecated. Please use --all instead. -t --filter: A filter that limits the update to the specified types of packages in the form of a comma-separated list of [platform, system-image, tool, platform-tool, doc, sample, source]. This also accepts the identifiers returned by 'list sdk --extended'. -n --dry-mode : Simulates the update but does not download or install anything. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.plugins.android_emulator.util.Utils.getToolCommand(Utils.java:369) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:413) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:406) at hudson.plugins.android_emulator.SdkInstaller.isPlatformInstalled(SdkInstaller.java:258) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:205) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:190) at hudson.plugins.android_emulator.SdkInstaller.installDependencies(SdkInstaller.java:177) at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:250) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:600) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) project=hudson.maven.MavenModuleSet@1a42f7f[absio-android-IT-4.2] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at hudson.plugins.android_emulator.util.Utils.getToolCommand(Utils.java:369) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:413) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:406) at hudson.plugins.android_emulator.SdkInstaller.isPlatformInstalled(SdkInstaller.java:258) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:205) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:190) at hudson.plugins.android_emulator.SdkInstaller.installDependencies(SdkInstaller.java:177) at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:250) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.do
[JIRA] (JENKINS-17429) Testing the new subject field
Kohsuke Kawaguchi commented on JENKINS-17429 Testing the new subject field testing after the full puppetization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17434|warnings) Allow to call parsers without jenkings
pescuma created JENKINS-17434 Allow to call parsers without jenkings Issue Type: New Feature Assignee: Ulli Hafner Components: warnings Created: 01/Apr/13 10:13 PM Description: Could you please create a project with the parsers, in a way that they could be used as a jar file (outside jenkins)? I'm asking that because I'm writing a tool to compute the build result without the need for a server and I'd like to use your parsers from the warnings plugin (if you want to check it out: https://github.com/pescuma/buildhealth ) Thank you, Pescuma Project: Jenkins Priority: Major Reporter: pescuma This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17433|sauce-ondemand) Sauce plugin 1.51 throws exceptions and causes builds to fail
R. Tyler Croy created JENKINS-17433 Sauce plugin 1.51 throws exceptions and causes builds to fail Issue Type: Bug Assignee: Ross Rowe Components: sauce-ondemand Created: 01/Apr/13 10:12 PM Description: We've run into this on the past two versions (1.51, 1.50) with some subset of jobs that use the Sauce plugin, generally only for the Sauce Connect integration. The error below is what is dumped to the "All Jenkins Log", the jobs that have the failure have completely empty Console Logs. SEVERE: #1705 failed to build and we don't even have a listener java.lang.NullPointerException at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:720) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Apr 1, 2013 3:07:31 PM hudson.model.Run handleFatalBuildProblem SEVERE: #1705 failed to build and we don't even have a listener java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.decorateLogger(SauceOnDemandBuildWrapper.java:514) at hudson.model.Run.execute(Run.java:1562) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Project: Jenkins Priority: Blocker Reporter: R. Tyler Croy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14302) Integration with the Build Pipeline Plugin
Marc Esher commented on JENKINS-14302 Integration with the Build Pipeline Plugin I put a bit of money where my mouth is on this one via the "Sponsor this" link... $100 bucks isn't much, but if others value this one as much as I do perhaps we could contribute enough to have this issue bubbled up to the top, worked on, and released. The build flow plugin is exactly what I was looking for – external job flow configuration – and integration with the Build Pipeline view is it's killer missing feature. http://www.freedomsponsors.org/core/offer/243/integration-with-the-build-pipeline-plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17429) Testing the new subject field
Kohsuke Kawaguchi commented on JENKINS-17429 Testing the new subject field Still struggling with overrides. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-17429) Testing the new subject field
Kohsuke Kawaguchi resolved JENKINS-17429 as Fixed Testing the new subject field This is now working. Change By: Kohsuke Kawaguchi (01/Apr/13 10:40 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] [sauce-ondemand] (JENKINS-17433) Sauce plugin 1.51 throws exceptions and causes builds to fail
Ross Rowe started work on JENKINS-17433 Sauce plugin 1.51 throws exceptions and causes builds to fail Change By: Ross Rowe (01/Apr/13 10:42 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-17433) Sauce plugin 1.51 throws exceptions and causes builds to fail
Ross Rowe resolved JENKINS-17433 as Fixed Sauce plugin 1.51 throws exceptions and causes builds to fail I've pushed version 1.52 to the Jenkins plugin repository, can you try this version out and let me know if it fixes the issue? Change By: Ross Rowe (01/Apr/13 10:54 PM) Status: In Progress 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] [testlink] (JENKINS-17146) Test link plugin is not looking trough my suite name options in testNG
Charles Agnello commented on JENKINS-17146 Test link plugin is not looking trough my suite name options in testNG I'm having the same issue with the Result Seeking strategy for Junit method name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-7960) EC2 Nodes which share an AMI ID get the wrong labels
Emil Sit commented on JENKINS-7960 EC2 Nodes which share an AMI ID get the wrong labels This does not work properly still with instance caps: instance caps are calculated solely based on AMI (see EC2Cloud#addProvisionedSlave), not based on template. So, if you have two types of slaves based on a common AMI but intended for different purpose, if the instance cap is low on one type, it may never get provisioned if the other type has many outstanding instances. I'm not sure an easy way around this particular issue; perhaps the template information could be stored on a provisioned instance as a tag? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-17435) FATAL: channel is already closed on Android Emulator launch
Sam Xiao created JENKINS-17435 FATAL: channel is already closed on Android Emulator launch Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 02/Apr/13 3:59 AM Description: Failure log 20:36:06 [android] Using Android SDK: /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test 20:36:06 [android] Creating Android AVD: /home/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd 20:36:06 [android] /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/tools/android create avd -f -a -c 128M -s WVGA800 -n hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -t "Google Inc.:Google APIs:7" 20:36:07 [android] Setting hardware properties: 20:36:07 hw.audioOutput: no 20:36:07 hw.audioInput: no 20:36:07 hw.ramSize: 512 20:36:07 vm.heapSize: 32 20:36:07 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb start-server 20:36:07 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/tools/emulator -snapshot-list -no-window -avd hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 20:36:07 [android] Starting Android emulator and creating initial snapshot 20:36:07 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/tools/emulator -no-boot-anim -ports 32814,35961 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-snapshot-update-time 20:36:10 * daemon not running. starting it now on port 34404 * 20:36:10 * daemon started successfully * 20:36:12 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb connect localhost:35961 20:36:12 [android] Waiting for emulator to finish booting... 20:36:12 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb -s localhost:35961 shell getprop dev.bootcomplete 20:36:12 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb connect localhost:35961 20:36:26 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb -s localhost:35961 shell getprop dev.bootcomplete 20:36:26 $ /home/jenkins/client-tools/symlinks/sdk_for_gerrit_client_android_test/platform-tools/adb connect localhost:35961 20:36:27 [android] Interrupted while waiting for emulator to finish booting. 20:36:27 [android] Emulator was shut down before it finished booting 20:36:27 FATAL: channel is already closed 20:36:27 hudson.remoting.ChannelClosedException: channel is already closed 20:36:27 at hudson.remoting.Channel.send(Channel.java:494) 20:36:27 at hudson.remoting.Request.call(Request.java:129) 20:36:27 at hudson.remoting.Channel.call(Channel.java:672) 20:36:27 at hudson.Launcher$RemoteLauncher.launch(Launcher.java:852) 20:36:27 at hudson.Launcher$ProcStarter.start(Launcher.java:353) 20:36:27 at hudson.plugins.android_emulator.AndroidEmulator.disconnectEmulator(AndroidEmulator.java:520) 20:36:27 at hudson.plugins.android_emulator.AndroidEmulator.cleanUp(AndroidEmulator.java:572) 20:36:27 at hudson.plugins.android_emulator.AndroidEmulator.cleanUp(AndroidEmulator.java:553) 20:36:27 at hudson.plugins.android_emulator.AndroidEmulator.doSetUp(AndroidEmulator.java:392) 20:36:27 at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:257) 20:36:27 at hudson.model.Build$BuildExecution.doRun(Build.java:154) 20:36:27 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) 20:36:27 at hudson.model.Run.execute(Run.java:1575) 20:36:27 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 20:36:27 at hudson.model.ResourceController.execute(ResourceController.java:88) 20:36:27 at hudson.model.Executor.run(Executor.java:237) 20:36:27 Caused by: java.io.IOException 20:36:27 at hudson.remoting.Channel.close(Channel.java:910) 20:36:27 at hudson.remoting.Channel.close(Channel.java:892) 20:36:27 at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:615) 20:36:27
