[JIRA] [maven] (JENKINS-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bob Verbrugge reopened JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 After installing Jenkins 1.525 the builds using jdk1.5.0_12 still fail with UnsupportedClassVersionError Change By: Bob Verbrugge (30/Jul/13 6:12 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bob Verbrugge commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 Notice that Jenkins-18403 break builds since 1.518, this issue arises after upgrade from 1.519 to 1.520 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-18995) GIT changelog shows all changes since first day
Pavel Kudrys created JENKINS-18995 GIT changelog shows all changes since first day Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: GITClientPlug.png Components: git-client Created: 30/Jul/13 6:37 AM Description: Since installing GIT Client plugin version 1.1 (and updated 1.1.1), Jenkins job now shows all changes since we started with GIT. See the attached picture (there is about 500 changes). It's quite annoying problem. All is OK after replacing the actual GIT Client plugin (1.1.1) with version 1.0.7. It's good workaround, but definitely not a permanent solution The job we are using consists of two building slaves. And the interesting point is, that the change log looks fine on 64bit slave (only changes since the previous build are shown), but on 32bit slave (and Jenkins Master machine) it shows all changes since start. Feel free to contact me in case you need more details. Project: Jenkins Priority: Major Reporter: Pavel Kudrys This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [audit-trail] (JENKINS-16938) Information lost when build is stopped by user (our case 8705)
Christian Wolfgang updated JENKINS-16938 Information lost when build is stopped by user (our case 8705) Change By: Christian Wolfgang (30/Jul/13 7:02 AM) Component/s: core Component/s: logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18179) Allow Build Hiding in Build History
Christian Wolfgang updated JENKINS-18179 Allow Build Hiding in Build History Removing the component "logging" since it has nothing to do with the logging plugin. Change By: Christian Wolfgang (30/Jul/13 7:05 AM) Component/s: logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18780) Renaming Project causes content encoding error
Christian Wolfgang updated JENKINS-18780 Renaming Project causes content encoding error Removing the component "logging" since it has nothing to do with the logging plugin. Change By: Christian Wolfgang (30/Jul/13 7:04 AM) Component/s: core Component/s: logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18456) Jenkins Job Current Log Status ( our case 9603)
Christian Wolfgang updated JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Removing the component "logging" since it has nothing to do with the logging plugin. Change By: Christian Wolfgang (30/Jul/13 7:03 AM) Component/s: plugin Component/s: logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-18996) Show parameter descriptions as part of project description
Thomas Vestergaard Trolle created JENKINS-18996 Show parameter descriptions as part of project description Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 30/Jul/13 7:07 AM Description: It would be really convenient, if the descriptions of the parameters could be displayed as part of the project description. I often find myself adding something like the following to my project descriptions: Parameters: ul libParameter1:/b Copy-paste of parameter1 description/li libParameter2:/b Copy-paste of parameter2 description/li libParameter3:/b Copy-paste of parameter3 description/li /ul It would be appreciated, if I didn't have too. How different people use the project description does of course vary. Regardless, I think, there should be some information on the project front-page about that it is parametrised - apart from the changed build link being changed to "Build with Parameters". Environment: All Project: Jenkins Priority: Minor Reporter: Thomas Vestergaard Trolle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Wolf Wolfswinkel commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Just upgraded to 1.525. Unfortunately the issue is still present for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18780) Renaming Project causes content encoding error
Christian Wolfgang updated JENKINS-18780 Renaming Project causes content encoding error Change By: Christian Wolfgang (30/Jul/13 7:33 AM) Summary: RenamingProjectcausescontentencodingerror ,case9772 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18780) Renaming Project causes content encoding error, case 9772
Christian Wolfgang updated JENKINS-18780 Renaming Project causes content encoding error, case 9772 Change By: Christian Wolfgang (30/Jul/13 7:32 AM) Summary: RenamingProjectcausescontentencodingerror ,case9772 Assignee: PraqmaSupport This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18179) Allow Build Hiding in Build History
Daniel Beck updated JENKINS-18179 Allow Build Hiding in Build History No indication that this is about Build Flow plugin or Logaction plugin. Also removing Nicolas as assignee, was probably automatic due to Build Flow. Change By: Daniel Beck (30/Jul/13 7:38 AM) Assignee: NicolasDeLoof Component/s: core Component/s: logaction Component/s: build-flow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18307) Multijob Schedule a Build Button in the Multijob view stopped working
Rotem G commented on JENKINS-18307 Multijob Schedule a Build Button in the Multijob view stopped working Oren, What is the Jenkins and MultiJob plug-in version you are using ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Daniel Draganov reopened JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved I was able to reproduce the issue. Jenkins version 1.522 I've tried to make it work with: $JENKINS_HOME/userContent/xunit/junitConverter.xsl fullPath to junitConverter.xsl placing the file in the workspace path placing the file in a lerative to the workspace path but with no success. Change By: Daniel Draganov (30/Jul/13 8:07 AM) Resolution: Fixed Status: Resolved Reopened Assignee: GregoryBoissinot EricAnker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Daniel Draganov edited a comment on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved I was able to reproduce the issue. Jenkins version 1.522 I've tried to make it work with: $JENKINS_HOME/userContent/xunit/junitConverter.xsl fullPath to junitConverter.xsl placing the file in the workspace path placing the file in a relative to the workspace path but with no success. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18997) Add @NoOwner job ownership filter
Oleg Nenashev created JENKINS-18997 Add @NoOwner job ownership filter Issue Type: Improvement Assignee: Unassigned Components: ownership Created: 30/Jul/13 8:18 AM Project: Jenkins Priority: Minor Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
Martin Olsson commented on JENKINS-18674 TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened This is still an issue for me in 1.525. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-import] (JENKINS-18998) Jobs are not loaded anymore after upgrading to version 1.525
Martin K. created JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 Issue Type: Bug Affects Versions: current Assignee: jieryn Components: job-import Created: 30/Jul/13 8:48 AM Description: After upgrading to version 1.525 Many of my jobs seem to fail loading. The log says the following: Jul 30, 2013 10:36:40 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job dacodi_model-production hudson.util.IOException2: Unable to read /home/tomcat7/.jenkins/jobs/dacodi_model-production/config.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.lang.NullPointerException cause-message : null class : org.jruby.runtime.builtin.IRubyObject required-type : org.jruby.runtime.builtin.IRubyObject converter-type : org.jenkinsci.jruby.JRubyXStreamConverter path: /project/buildWrappers/ruby-proxy-object/ruby-object line number : 125 class[1]: org.jenkinsci.jruby.JRubyMapper$DynamicProxy converter-type[1] : org.jenkinsci.jruby.JavaProxyConverter class[2]: hudson.util.DescribableList converter-type[2] : hudson.util.DescribableList$ConverterImpl class[3]: hudson.model.FreeStyleProject converter-type[3] : hudson.util.RobustReflectionConverter version : null --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at org.jenkinsci.jruby.JavaProxyConverter.unmarshal(JavaProxyConverter.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:263) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at
[JIRA] [plugin] (JENKINS-18999) Installing CVS plugin v2.9 makes jobs that use the CVS plugin disappear
Paul Croome created JENKINS-18999 Installing CVS plugin v2.9 makes jobs that use the CVS plugin disappear Issue Type: Bug Affects Versions: current Assignee: Michael Clarke Components: plugin Created: 30/Jul/13 8:53 AM Description: I have 6 Jenkins jobs that use the CVS plugin. When I updated the CVS plugin from v2.8 to v2.9, all of these 6 jobs disappeared from my Jenkins dashboard. When I downgraded to v2.8, the jobs reappeared. Here is the relevant part of a typical configuration file: scm class="hudson.scm.CVSSCM" plugin="cvs@2.8" flattenfalse/flatten repositoryBrowser class="hudson.scm.browsers.ViewCVS" urlhttp://lagoon.hq.sag/cgi-bin/viewvc/viewvc.cgi//url /repositoryBrowser repositories hudson.scm.CvsRepository cvsRoot:pserver:anonym...@lagoon.hq.sag:2401/FS/fs3073/Repositories/DocSources/cvsRoot repositoryItems hudson.scm.CvsRepositoryItem modules hudson.scm.CvsModule localName/localName remoteNameOwwep-cep-clientapi/remoteName /hudson.scm.CvsModule /modules location class="hudson.scm.CvsRepositoryLocation$HeadRepositoryLocation" locationTypeHEAD/locationType useHeadIfNotFoundfalse/useHeadIfNotFound /location /hudson.scm.CvsRepositoryItem /repositoryItems compressionLevel-1/compressionLevel excludedRegions hudson.scm.ExcludedRegion pattern/pattern /hudson.scm.ExcludedRegion /excludedRegions passwordRequiredfalse/passwordRequired /hudson.scm.CvsRepository /repositories canUseUpdatefalse/canUseUpdate skipChangeLogfalse/skipChangeLog pruneEmptyDirectoriestrue/pruneEmptyDirectories disableCvsQuiettrue/disableCvsQuiet cleanOnFailedUpdatefalse/cleanOnFailedUpdate forceCleanCopyfalse/forceCleanCopy /scm Project: Jenkins Priority: Major Reporter: Paul Croome This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18959) /log/all polluted with FINE* messages from other loggers
James Howe commented on JENKINS-18959 /log/all polluted with FINE* messages from other loggers It's less confusing for /log/all not to show all logs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-import] (JENKINS-18998) Jobs are not loaded anymore after upgrading to version 1.525
Martin K. commented on JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 here is what I think the real problem is, namley the rvm plugin seems to be missing: SEVERE: Failed Loading plugin rvm java.io.IOException: Dependency ruby-runtime (0.7) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479) 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:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Jul 30, 2013 11:00:13 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin ruby-runtime hudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:379) at hudson.PluginManager$2$1$1.run(PluginManager.java:334) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: org.jruby.embed.EvalFailedException: java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:141) at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1231) at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1224) at org.kohsuke.stapler.jelly.jruby.haml.HamlLanguage.createContainer(HamlLanguage.java:28) at org.kohsuke.stapler.jelly.jruby.JRubyFacet.init(JRubyFacet.java:71) at ruby.RubyRuntimePlugin.registerJRubyFacet(RubyRuntimePlugin.java:39) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:30) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:387) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:376) ... 9 more Caused by: java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected at com.kenai.jaffl.provider.jffi.AsmRuntime.marshal(AsmRuntime.java:169) at org.jruby.ext.posix.LinuxLibC$jaffl$0.setenv(Unknown Source) at org.jruby.ext.posix.BaseNativePOSIX.setenv(BaseNativePOSIX.java:221) at org.jruby.ext.posix.LazyPOSIX.setenv(LazyPOSIX.java:263) at org.jruby.RubyGlobal$StringOnlyRubyHash.case_aware_op_aset(RubyGlobal.java:176) at org.jruby.RubyGlobal$CaseInsensitiveStringOnlyRubyHash.op_aset(RubyGlobal.java:87) at org.jruby.RubyHash$i$2$0$op_aset.call(RubyHash$i$2$0$op_aset.gen:65535) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:203) at org.jruby.ast.AttrAssignTwoArgNode.interpret(AttrAssignTwoArgNode.java:42) at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104) at org.jruby.ast.BlockNode.interpret(BlockNode.java:71) at org.jruby.ast.RootNode.interpret(RootNode.java:129) at org.jruby.evaluator.ASTInterpreter.INTERPRET_ROOT(ASTInterpreter.java:120) at org.jruby.Ruby.runInterpreter(Ruby.java:720) at org.jruby.Ruby.runInterpreter(Ruby.java:728) at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:119) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group
[JIRA] [maven] (JENKINS-18922) Upgrading to 1.524 (Upgrade Automatically) breaks jenkins
Régis Desgroppes commented on JENKINS-18922 Upgrading to 1.524 (Upgrade Automatically) breaks jenkins +1 with the Job History 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] [job-import] (JENKINS-18998) Jobs are not loaded anymore after upgrading to version 1.525
Martin K. commented on JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 Looks like this is related to this: https://github.com/elvanja/jenkins-gitlab-hook-plugin/issues/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-lint] (JENKINS-17584) Copy source file fails with maven build
Martin Krischik commented on JENKINS-17584 Copy source file fails with maven build Tried android.lint.fullpath — did not help. I guess for now I have to switch Publish “Android Lint results” off. To bad. Would have been useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-import] (JENKINS-18998) Jobs are not loaded anymore after upgrading to version 1.525
Martin K. commented on JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 For now I just commented out the part where the plugin is loaded within the config.xml files so the jobs are showing up again. I'm not sure If my setup will still work without RVM plugin, I need to test that. Part that was commented out within the projects: ruby-proxy-object ruby-object ruby-class="Jenkins::Plugin::Proxies::BuildWrapper" pluginid="rvm" object ruby-class="RvmWrapper" pluginid="rvm" impl pluginid="rvm" ruby-class="String"ruby-2.0.0-p195@model/impl /object pluginid pluginid="rvm" ruby-class="String"rvm/pluginid /ruby-object /ruby-proxy-object This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-12017) Seriously slow rendering/loading times for the job/foo/configure page
deyan pavlov edited a comment on JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page An issue for me, too. Takes 45 seconds to load configuration page. Available are around 30 plugins but plugin number didn't change for long time and this issue appeared just after upgrade to 1.523. Solved the issue by uninstalling the "timestamper" plugin which was obviously causing the slowdown. P.S. after some time this issue appeared again. So it might not have been due to this particular 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-18959) /log/all polluted with FINE* messages from other loggers
Jesse Glick commented on JENKINS-18959 /log/all polluted with FINE* messages from other loggers Well /log/all never shows all log records; by default it always shows everything logged at INFO and above (after a fix I made a few months ago to not restrict it to hudson. and jenkins. namespaces); but then it was also showing FINE and lower records that were only being logged at all because other /log/* loggers had been configured to show them. This is because in java.util.logging, to receive log records you need to both set the level of the logger low enough and attach a handler to it, but these are separate acts: all handlers attached to the logger will receive the same records. So this fix tries to avoid sending the finer log records to all when they are already being displayed somewhere else, currently just by limiting all to INFO and above. It probably needs some adjustment since you can also—IMHO quite confusingly—adjust levels of arbitrary loggers in the Jenkins UI without adding a /log/* logger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-18994) fatal null point exeption when running Running cleartool setcs to update clearcase view
Vincent Latombe commented on JENKINS-18994 fatal null point exeption when running Running cleartool setcs to update clearcase view Could you provide the output for 'cleartool setcs -current -overwrite' in the same directory? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19000) Something broken in 1.525 (issue loading maven plugin?)
Ben Golding created JENKINS-19000 Something broken in 1.525 (issue loading maven plugin?) Issue Type: Bug Assignee: Unassigned Components: core, maven Created: 30/Jul/13 11:05 AM Description: I was unable to update core 1.522 to 1.525. The Jenkins webpage shows the error below. Rolling back to the old jenkins.war fixed it. org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:906) at jenkins.model.Jenkins.init(Jenkins.java:806) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.NoClassDefFoundError: hudson/maven/MavenModule at hudson.plugins.jobConfigHistory.JobConfigHistory.isSaveable(JobConfigHistory.java:426) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:28) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.UpdateCenter.save(UpdateCenter.java:519) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList._onModified(PersistedList.java:181) at hudson.util.PersistedList.add(PersistedList.java:72) at hudson.model.UpdateCenter.load(UpdateCenter.java:549) at hudson.model.UpdateCenter.init(UpdateCenter.java:1546) ... 13 more Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenModule at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 22 more Project: Jenkins Priority: Blocker Reporter: Ben Golding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] [core] (JENKINS-19000) Something broken in 1.525 (issue loading maven plugin?)
Ben Golding commented on JENKINS-19000 Something broken in 1.525 (issue loading maven plugin?) Please advise how I could help to debug the root cause... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
stephen callagahn commented on JENKINS-18638 Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser still present on 1.525. Would love to have this resolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pollscm] (JENKINS-19001) Git polling not detecting changes since 1.1.1
Moosh Ben created JENKINS-19001 Git polling not detecting changes since 1.1.1 Issue Type: Bug Assignee: Vincent Latombe Components: pollscm Created: 30/Jul/13 11:27 AM Description: Git polling not detecting changes since 1.1.1. Seems to be related to "Excluded Users" feature. Reverting to 1.0.7 fixed the issue. Am getting in the git polling log the following: Started on Jul 30, 2013 2:21:29 PM Using strategy: Default [poll] Last Built Revision: Revision AAA (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from origin Polling for changes in Ignored commit BBB: Found excluded author: Build System Done. Took 0.21 sec No changes BBB is the SHA ID of a new commit that shouldn't be ignored. Project: Jenkins Priority: Major Reporter: Moosh Ben This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-19001) Git polling not detecting changes since 1.1.1
Moosh Ben updated JENKINS-19001 Git polling not detecting changes since 1.1.1 Change By: Moosh Ben (30/Jul/13 11:28 AM) Component/s: git-client Component/s: pollscm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-19001) Git polling not detecting changes since 1.1.1
Moosh Ben updated JENKINS-19001 Git polling not detecting changes since 1.1.1 Change By: Moosh Ben (30/Jul/13 11:29 AM) Assignee: VincentLatombe NicolasDeLoof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Miquel Serralta
reopened JENKINS-18812
Redeployment feature
Hi Raphael. I think it does not work 100%.
I'm not able to use the {wl.source} variable. When I use it, it is not replaced by the proper string.
Moreover, I tried to specify the absolute path where my ear file is created, but it is treated as relative path.
The custom command I use looks like:
-debug -remote -verbose -upload -name UniVicWorkspace -source "/root/.jenkins/jobs/PGU TEST/workspace/UniVic.ear" -targets {wl.targets} -adminurl t3://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -redeploy
It chashes and in the log you can see weblogic.deploy.api.internal.utils.DeployerHelperException: The source file '/home/oracle/Oracle/Middleware/user_projects/domains/uvic/"/root/.jenkins/jobs/PGU' does not exist and cannot be deployed.
Thanks again. Nice job!
Change By:
Miquel Serralta
(30/Jul/13 11:29 AM)
Resolution:
Fixed
Status:
Resolved
Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Miquel Serralta commented on JENKINS-18812 Redeployment feature Sorry. I didn't see the issue #JENKINS-18940. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Miquel Serralta resolved JENKINS-18812 as Fixed Redeployment feature #JENKINS-18940 Change By: Miquel Serralta (30/Jul/13 11:45 AM) Status: Reopened 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-18776) @QueryParameter with @RelativePath broken
Oliver Gondža commented on JENKINS-18776 @QueryParameter with @RelativePath broken I'm sorry but what needs to be backported to get this lts-candidate 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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option
ben patterson resolved JENKINS-11023 as Fixed Add Wipe out workspace option Fixed/released in v 1.4.4. Now, in the process of shelving, a workspace will be wiped out before the project is zipped. Change By: ben patterson (30/Jul/13 12:05 PM) Status: InProgress Resolved Fix Version/s: current 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] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option
ben patterson commented on JENKINS-11023 Add Wipe out workspace option Brian - I did not look at the HTTP GET option, but the workspace wipeout happens within the context of the shelving itself, so I would expect this to solve your problem as well. If it does not, please open another ticket for that particular flavor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-11023) Add Wipe out workspace option
ben patterson closed JENKINS-11023 as Fixed Add Wipe out workspace option Release 1.4.4 Change By: ben patterson (30/Jul/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] [parameters] (JENKINS-2664) Private Parameters (i.e. Not saving parameters)
Maciej Jaros closed JENKINS-2664 as Fixed Private Parameters (i.e. Not saving parameters) Works fine in 1.480 Change By: Maciej Jaros (30/Jul/13 12:28 PM) Status: Open Closed 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] [parameters] (JENKINS-2664) Private Parameters (i.e. Not saving parameters)
Maciej Jaros commented on JENKINS-2664 Private Parameters (i.e. Not saving parameters) This seem to be resolved with PasswordParameter. Saved value is encrypted before saving to build.xml (which should not be accessible anyway). It's also inaccessible from Jenkins build page (plain text stars are shown with what seems a random number of characters). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18998) Jobs are not loaded anymore after upgrading to version 1.525
jieryn updated JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 Change By: jieryn (30/Jul/13 12:32 PM) Assignee: jieryn Component/s: core Component/s: job-import This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Damian Klimowicz commented on JENKINS-18714 SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable SVN_URL and SVN_REVISION are missing also when "Advanced Project Options - Use custom workspace" is set by variable. Jenkins ver. 1.525 with Subversion Plug-in 1.50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-19002) Grouping parameters for build form page
Maciej Jaros created JENKINS-19002 Grouping parameters for build form page Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: parameters Created: 30/Jul/13 12:39 PM Description: Some builds can have a lot of parameters. It would easier for users to fill out the form if they would be grouped. On configuration page add group start box with: id of the group name of the group (optional, if not given id is used) is collapseable (checkbox) is collapsed by default (checkbox) On the form page add accordion styled groups (like the one available in jQuery UI). Project: Jenkins Priority: Major Reporter: Maciej Jaros This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-19002) Grouping parameters for build form page
Maciej Jaros updated JENKINS-19002 Grouping parameters for build form page Change By: Maciej Jaros (30/Jul/13 12:41 PM) Description: Somebuildscanhavealotofparameters.Itwouldeasierforuserstofillouttheformiftheywouldbegrouped.Onconfigurationpageaddgroupstartboxwith:*idofthegroup*nameofthegroup(optional,ifnotgivenidisused)*iscollapseable(checkbox)*iscollapsedbydefault(checkbox) Groupcontinuesuntiltheendofparamsorgroupendboxornextgroupstartbox. Ontheformpageaddaccordionstyledgroups(liketheoneavailableinjQueryUI). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18998) Jobs are not loaded anymore after upgrading to version 1.525
Martin K. commented on JENKINS-18998 Jobs are not loaded anymore after upgrading to version 1.525 Looks like it does indeed work also without the RVM plugin. Does jenkins somehow now also respect the .ruby-version and .ruby-gemset natively? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Raphael CHAUMIER commented on JENKINS-18812 Redeployment feature The bug has been fixed in 2.5 The plugin finds the resource file to deploy according to the job configuration whatever the command line you set. Even if you specify the resource directly, the plugin tries to detect the resource file to deploy before executing task in the same way as you didn't ovveride command. Let see the documentation for further information. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
Robert Hook commented on JENKINS-18674 TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened Definite issue still in 1.525 - I found that if I disabled the plot plugin, then the configuration screen will work, but of course the plot configurations will be lost. We can work around this short term by preserving the plot plugin configuration from the xml file, and reinstating it later when this issue has been resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
SCM/JIRA link daemon commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScript.java http://jenkins-ci.org/commit/postbuildscript-plugin/754a85cb515de0f07de2cb186753ef789bd18c8e Log: FIXED JENKINS-11219 don't run on MatrixAgregator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18387) Jenkins sometimes fails to restart successfully
K P commented on JENKINS-18387 Jenkins sometimes fails to restart successfully I'm also having issues with automatic restarting, though the scenario is different. So I don't know if it's related. jenkins 1.524, running as Windows service on Win XP. But I'm seeing this for many months now, so quite a number of versions back. It happens when auto-restarting jenkins, e.g. after doing the auto upgrade of jenkins or plugins. By the way, I get a Windows Visual Studio debugging Window (vs7jit.exe) showing that "An exception 'System.IO.IOException' has occurred in .NET Application". E.g. when auto-upgrading in 1.524: jenkins downloads 1.525 war, then tries to restart, which yields the .NET exception, consequently looking in Process Explorer: the new java.exe is started outside the jenkins.exe (not as child process) and jenkins.exe and old java.exe are stopped (the new java.exe runs in the background, but not under the Windows service anymore, which is stopped.) i.e. the java.exe process is uncontrollable (only visible in process list), until it is killed after that, the Windows service (jenkins) can be restarted, which will successfully spawn a child java.exe, as expected. (Note: often it seems to start the old .war on first manual restart, but I haven't reproduced this in detail. Often I had to copy the .war manually, or it may have worked on 2nd restart) In short: auto-upgrade actually isn't working correctly with the Windows service. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
SCM/JIRA link daemon resolved JENKINS-11219 as Fixed Add the option to run the script after all the sub elements of a matrix project build have finished Change By: SCM/JIRA link daemon (30/Jul/13 12:52 PM) Status: Reopened 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-19003) 100% CPU Java usage deadlock when queueing up jobs
L DоЬrοgοѡѕkі created JENKINS-19003 100% CPU Java usage deadlock when queueing up jobs Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: java_100CPU_jenkins_dump.tar.gz Components: core Created: 30/Jul/13 1:03 PM Description: The deadlock appears when a few builds are queued up at once. It seems to appear a bit at random, since sometimes all of the jobs can be queued up and built without problems, sometimes Jenkins hangs after 10 builds are queued, sometimes after 80. Therefore I was unable to provide an isolated, reproducible example. After the deadlock occurs, the java process running jenkins shows up as taking 100% of CPU in "top" console output. It is impossible to get a working HTTP connection to jenkins, "jstack PID" doesn't work as well. However, jstack -F PID and kill -3 PID worked and their output is attached to this report (a bit redundant maybe, especially since I called "kill -3 PID" thrice and probably three dumps are there in stdout log). To kill the java process, "kill -9 PID" was necessary. Environment: Most environment details are in file environment.log inside attached tarball. The ones not included there: * OS: Ubuntu Server 10.04.3 LTS * RAM: 24 GB * CPU: Intel Xeon E5620 Project: Jenkins Priority: Critical Reporter: L DоЬrοgοѡѕkі This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-19002) Grouping parameters for build form page
Maciej Jaros updated JENKINS-19002 Grouping parameters for build form page Screen with two groups (and first parameter not groupped in any way). Change By: Maciej Jaros (30/Jul/13 1:06 PM) Attachment: jenkins-groups-configuration.png.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-18981) Can't add a build step using the Google Chrome browser
Paolo Sacconier commented on JENKINS-18981 Cant add a build step using the Google Chrome browser I can confirm the same issue, but I'm using the current chrome beta (my Jenkins instance is running on Ubuntu installed from the official jenkins repo, but I don't think it's relevant to the issue). Since I updated to 1.525 I can't even log in. With firefox current and safari it's working fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19004) Channel's executorService's pool should have a name
kutzi created JENKINS-19004 Channels executorServices pool should have a name Issue Type: Improvement Assignee: Unassigned Components: core Created: 30/Jul/13 1:11 PM Description: In Jenkins thread dump I can see something like this: pool-4-thread-18865 "pool-4-thread-18865" Id=375223 Group=main TIMED_WAITING on java.util.concurrent.SynchronousQueue$TransferStack@1412ebc5 at sun.misc.Unsafe.park(Native Method) waiting on java.util.concurrent.SynchronousQueue$TransferStack@1412ebc5 at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:424) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:323) at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:874) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:955) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:917) at java.lang.Thread.run(Thread.java:662) pool-4-thread-18866 "pool-4-thread-18866" Id=375224 Group=main BLOCKED on com.thoughtworks.xstream.mapper.AnnotationMapper$WeakHashSet@41deb94c owned by "pool-4-thread-18870" Id=375228 My guess is, that these pools are the tread pools of the executors asssociated to channels as constructred e.g. in Launcher#main Would be nice, if theses pools/threads would have non-generic name - i.e. names which make it obvious where the threads come form Project: Jenkins Labels: remoting Priority: Major Reporter: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-19002) Grouping parameters for build form page
Maciej Jaros edited a comment on JENKINS-19002 Grouping parameters for build form page Attached screen (example visual implementation) with two groups (and first parameter not grouped in any way). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19003) 100% CPU Java usage deadlock when queueing up jobs
L Dоbrοgοwѕkі updated JENKINS-19003 100% CPU Java usage deadlock when queueing up jobs Change By: L Dоbrοgοwѕkі (30/Jul/13 1:12 PM) Environment: Mostenvironmentdetailsareinfileenvironment.loginsideattachedtarball.Theonesnotincludedthere:* Jenkins1.522* OS:UbuntuServer10.04.3LTS*RAM:24GB*CPU:IntelXeonE5620 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-19002) Grouping parameters for build form page
Maciej Jaros updated JENKINS-19002 Grouping parameters for build form page Change By: Maciej Jaros (30/Jul/13 1:14 PM) Description: Somebuildscanhavealotofparameters.Itwouldeasierforuserstofillouttheformiftheywouldbegrouped.Onconfigurationpageaddgroupstartboxwith:* del idofthegroup /del *nameofthegroup del (optional,ifnotgivenidisused) /del *iscollapseable(checkbox)*iscollapsedbydefault(checkbox)Groupcontinuesuntiltheendofparamsorgroupendboxornextgroupstartbox.Ontheformpageaddaccordionstyledgroups(liketheoneavailableinjQueryUI). EDIT:Onsecondthoughtidisnotneededunlesswewouldwanttohavegroupsinsidegroups. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19004) Channel's executorService's pool should have a name
kutzi commented on JENKINS-19004 Channels executorServices pool should have a name On a slightly related note I wonder if it is good that the the ExecutorService in Launcher#main is created as a cached thread pool executor. I guess that is reason for the insanely high thread numbers (18866+) and probably also worsens the impact of contention bugs like JENKINS-13154 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19003) 100% CPU Java usage deadlock when queueing up jobs
L Dоbrοgοwѕkі updated JENKINS-19003 100% CPU Java usage deadlock when queueing up jobs Change By: L Dоbrοgοwѕkі (30/Jul/13 1:13 PM) Environment: Mostenvironmentdetailsareinfileenvironment.log inside inthe attachedtarball.Theonesnotincludedthere:*Jenkins1.522*OS:UbuntuServer10.04.3LTS*RAM:24GB*CPU:IntelXeonE5620 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19004) Channel's executorService's pool should have a name
kutzi assigned JENKINS-19004 to kutzi Channels executorServices pool should have a name Change By: kutzi (30/Jul/13 1:15 PM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Petr Prochazka commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. I have same problem with v1.525. We use PWAuth plugin too with policy "Logged-in users can do anything". Environment: OpenSUSE 11.4 x86_64 Oracle Java 1.6.0_45 Tomcat 6.0.32 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Now I have correct date 2 weeks in the future, but anyway I have to login 10 times a day because I often become logged out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Simone Livraghi created JENKINS-19005 Cannot deploy on Artifactory Issue Type: Bug Affects Versions: current Assignee: yossis Attachments: config.xml, log Components: artifactory, deploy, maven Created: 30/Jul/13 1:29 PM Description: I have create a new webapp project. mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-webapp I have committed the project into a git repository. I have create a new "Build a maven2/3 project" job on jenkins that perform the git clone and the mvn install. It works. I added a post build action (type: Deploy artifacts to Artifactory). Now the build fails. java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:174) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ExceptionInInitializerError at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:101) at hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded(Maven3Builder.java:297) at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:137) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:170) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) ... 18 more Caused by: sun.misc.InvalidJarIndexException: Invalid index at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:858) at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:765) at sun.misc.URLClassPath.getResource(URLClassPath.java:169) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:386) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromParent(ClassRealm.java:405) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:46) at
[JIRA] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Simone Livraghi edited a comment on JENKINS-19005 Cannot deploy on Artifactory Jenkins version: 1.525 Jenkins Artifactory Plugin version: 2.1.6 Maven Integration plugin version: 1.525 Artifactory version: 3.0.1 (rev. 30008) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Simone Livraghi commented on JENKINS-19005 Cannot deploy on Artifactory Jenkins version: 1.525 Jenkins Artifactory Plugin version: 2.1.6 Maven Integration plugin version: 1.525 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-12921) Trigger fails to build with Null value not allowed as an environment variable: GIT_BRANCH error
rsandell updated JENKINS-12921 Trigger fails to build with Null value not allowed as an environment variable: GIT_BRANCH error Change By: rsandell (30/Jul/13 1:33 PM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-12921) Trigger fails to build with Null value not allowed as an environment variable: GIT_BRANCH error
rsandell commented on JENKINS-12921 Trigger fails to build with Null value not allowed as an environment variable: GIT_BRANCH error It is the Git plugin that wants to add an env var to the build during checkout but fails at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) If you fill in a branch value in the git config section, you could put whatever you want here I think. I usually jut put in master, since the choosing strategy will check out a specific revision anyways. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
William Whittle commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) I'm also seeing this on 1.525 running on CentOS 6.3 (EC2 AMI: ami-eb0b8082). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
William Whittle edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) I'm also seeing this on 1.525 running on CentOS 6.3 (EC2 AMI: ami-eb0b8082). I don't see the issue when running the same Jenkins build on Windows 7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Simone Livraghi updated JENKINS-19005 Cannot deploy on Artifactory maven project Change By: Simone Livraghi (30/Jul/13 1:41 PM) Attachment: sample.tar.gz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-19005) Cannot deploy on Artifactory
Simone Livraghi edited a comment on JENKINS-19005 Cannot deploy on Artifactory sample.tar.gz contains the sample maven projec that fail the 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Tadas Subonis commented on JENKINS-18667 NullPointerException when saving job config I could actually fix this bug - it looks more or less about missing Job reference when we actually want Project. Maybe Gregory Boissinot could advice me on this? I am mainly concerned why we are accessing Job instance when we are saving project - it shouldn't be available until we actually start building project. Also, I would like to know how do we handle Trigger lifecycle. When do we get available project actions? How do we insert data and use constructor "DataBoundConstructor"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr
commented on JENKINS-18641
People View does Not Populate (makeStaplerProxy)
Confirmed this bug is not Fixed. I am running 1.525 on Ubuntu 12.04 Server + Chrome browser:
Includes all known “users”, including login identities which the current security realm can enumerate, as well as people mentioned in commit messages in recorded changelogs.
makeStaplerProxy('/$stapler/bound/a7d06408-0c93-483a-8910-c36b2295fa1f','154d0cb7-97a2-4f82-abda-bd46caf6ff29',news), display);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr reopened JENKINS-18641 People View does Not Populate (makeStaplerProxy) Does not appear to be fixed in 1.525. Change By: Shannon Kerr (30/Jul/13 2:12 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
David Ishee commented on JENKINS-18929 OutOfMemoryError: PermGen space Stats after 4 days: Attaching to process ID 32633, please wait... Debugger attached successfully. Server compiler detected. JVM version is 14.3-b01 using thread-local object allocation. Parallel GC with 4 thread(s) Heap Configuration: MinHeapFreeRatio = 40 MaxHeapFreeRatio = 70 MaxHeapSize = 1572864000 (1500.0MB) NewSize = 2686976 (2.5625MB) MaxNewSize = 17592186044415 MB OldSize = 5439488 (5.1875MB) NewRatio = 2 SurvivorRatio= 8 PermSize = 21757952 (20.75MB) MaxPermSize = 268435456 (256.0MB) Heap Usage: PS Young Generation Eden Space: capacity = 442761216 (422.25MB) used = 75178976 (71.69625854492188MB) free = 367582240 (350.5537414550781MB) 16.979575735919923% used >From Space: capacity = 39649280 (37.8125MB) used = 26526064 (25.297225952148438MB) free = 13123216 (12.515274047851562MB) 66.90175458419421% used To Space: capacity = 38666240 (36.875MB) used = 0 (0.0MB) free = 38666240 (36.875MB) 0.0% used PS Old Generation capacity = 227737600 (217.1875MB) used = 216759608 (206.71807098388672MB) free = 10977992 (10.469429016113281MB) 95.17954347459532% used PS Perm Generation capacity = 112787456 (107.5625MB) used = 91758560 (87.50778198242188MB) free = 21028896 (20.054718017578125MB) 81.35528830440151% used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-pipeline] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
peter bollen commented on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesnt exist. I'm having the same issue for build-pipeline 1.3.5 on Jenkins ver. 1.482. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-18837) Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion)
hydraswitch commented on JENKINS-18837 Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion) I'm having this problem as well. Do we know what version of Jenkins introduced this? Previously, I was using 1.512. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvfb] (JENKINS-19006) Add option to start a program/windowmanager with Xvfb
Julian M. created JENKINS-19006 Add option to start a program/windowmanager with Xvfb Issue Type: Improvement Affects Versions: current Assignee: zregvart Components: xvfb Created: 30/Jul/13 2:54 PM Description: Currently, the xvfb plugin always starts without a window manager. This causes errors/problems with the focus change in some test libraries like Fest (using the java.awt.robot). If you start a window manager yourself between xvfb and the surefire plugin, the errors are gone. It would be great if you would have a textfield in the global configuration of the plugin, where you can execute a program/window manager after xvfb is started. I am not sure that the display variable has to be exported for it to work. Currently, running this before our tests and after xvfb has started prevents the errors: export DISPLAY=:99 twm Project: Jenkins Labels: xvfb windowmanager Priority: Major Reporter: Julian M. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19007) copy artifacts via permalink for promoted builds shows wrong link
Joshua Ayson created JENKINS-19007 copy artifacts via permalink for promoted builds shows wrong link Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact, promoted-builds Created: 30/Jul/13 2:58 PM Description: Within the Copy Artifiact plugin you can select "Sepcified by permalink" and after installing the Promoted Builds plugin it lists as the last entry "Latest Promotion ...". What I see now as the Latest promotion is the promotion link to the project I'm in, instead of the referenced link specified in the Copy Artifacts from another project's referenced project. When I last upgraded Jenkins and the plugins a couple weeks ago this stopped working. It looks like a similar bug was reported on 9/9/2012: JENKINS-15086. Environment: Jenkins 1.523, Jenkins Promoted Builds Plugin 2.11, Copy Artifact Plugin 1.27 Project: Jenkins Labels: copyartifact promoted-builds permalink Priority: Major Reporter: Joshua Ayson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-10686) Polling on slaves can hang
Brian Smith commented on JENKINS-10686 Polling on slaves can hang OK. I will change the jobs to poll from the master. We are currently using the 1.509.1 LTS version and this issue occurs once every 3-4 weeks or so. Maybe the error message should be changed and/or the option to use the slaves to do the polling should be removed since that doesn't seem to be a valid option any more? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-18837) Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion)
sogabe commented on JENKINS-18837 Bad version number in .class file (Failed to load hudson.slaves.SlaveComputer$SlaveVersion) Since 1.520, Jenkins requires at least JDK 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] [perforce] (JENKINS-10686) Polling on slaves can hang
Rob Petti commented on JENKINS-10686 Polling on slaves can hang Which perforce plugin version are you using? That's the more important factor here, not the Jenkins version. Using slaves for polling is a valid option provided you have a solid connection to them, and they are not transient in nature. Which error message are you referring to? There are no error messages included in this ticket description. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17852) Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date).
Honza Brázdil resolved JENKINS-17852 as Fixed Pull request API information is not fully populated on older versions of the API (enterprise versions could be out of date). Change By: Honza Brázdil (30/Jul/13 3:05 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] [perforce] (JENKINS-10686) Polling on slaves can hang
Brian Smith commented on JENKINS-10686 Polling on slaves can hang Good point We are using 1.3.17 of the Perforce Plugin which is about a year old but after the original dates in this JIRA entry. I didn't see anything in the latest change notes related to polling so I haven't tried updating the plugin yet as a potential problem solving route. We are seeing the same error message as in the original post above - "There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. Check if your polling is hanging, and/or increase the number of threads if necessary.". I scoured the internet looking for ways to "increase the number of threads" and hit a dead end. My further searches ended up finding this old JIRA entry that seemed to be right in line with the problem we are seeing. All of our nodes are currently local to our building so our connection to them should be on the solid side. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18776) @QueryParameter with @RelativePath broken
Jesse Glick commented on JENKINS-18776 @QueryParameter with @RelativePath broken I just looked in https://github.com/jenkinsci/jenkins/compare/jenkins-1.524...jenkins-1.525 to try to figure out where the purported fix was, but there are no changes here except version number! Did the release process go haywire? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Nigel Stewart commented on JENKINS-18667 NullPointerException when saving job config Same problem here with Jenkins 1.525 RPM on Fedora 15 x86_64. Any suggested workarounds? A known good RPM? Nigel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-10686) Polling on slaves can hang
Rob Petti
commented on JENKINS-10686
Polling on slaves can hang
Yeah, you will want to update the perforce plugin to the latest. There should have been connectivity improvements since then.
That error message is a warning generated by Jenkins Core, so we can't change it. If it shows up, then you will need to restart Jenkins or kill you polling threads. You can kill threads using the following system groovy script:
Thread.getAllStackTraces().keySet().each(){ item -
if(item.getName().contains("SCM polling")){ println "Interrupting thread " + item.getId() + " " + item.getName(); item.interrupt() }
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-10686) Polling on slaves can hang
Rob Petti
edited a comment on JENKINS-10686
Polling on slaves can hang
Yeah, you will want to update the perforce plugin to the latest. There should have been connectivity improvements since then.
That error message is a warning generated by Jenkins Core, so we can't change it. If it shows up, then you will need to restart Jenkins or kill your polling threads. You can kill threads using the following system groovy script:
Thread.getAllStackTraces().keySet().each(){ item -
if(item.getName().contains("SCM polling")){ println "Interrupting thread " + item.getId() + " " + item.getName(); item.interrupt() }
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-18776) @QueryParameter with @RelativePath broken
Jesse Glick commented on JENKINS-18776 @QueryParameter with @RelativePath broken Anyway https://github.com/stapler/stapler/commit/fb1fa99985058151732a73c1a071383dbd20e116 is the fix, in Stapler 1.214. That was integrated in https://github.com/jenkinsci/jenkins/commit/fc836c135e2bba4fa66239ef42e8b542298cdbd9 and apparently required several follow-up test fixes in https://github.com/jenkinsci/jenkins/compare/efc0ca16fb975229afba1917b03eee160ce68986...504dadca61353bbbf393d4353200330455930e88 (I am guessing). Seems this is really in 1.526, since 1.525 was just botched. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick resolved JENKINS-18641 as Fixed People View does Not Populate (makeStaplerProxy) I think there is nothing wrong with the fix, it is just in 1.526, not 1.525 which is in fact identical to 1.524. Change By: Jesse Glick (30/Jul/13 3:30 PM) Status: Reopened 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] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Johannes Ohlemacher assigned JENKINS-18950 to Johannes Ohlemacher valgrind-plugin makes jenkins run out of memory under heavy use Change By: Johannes Ohlemacher (30/Jul/13 3:32 PM) Assignee: MarcoMiller JohannesOhlemacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) OK, thanks Jesse. When I looked at the package size for Ubuntu, I did see the 1.525 was slightly larger than 1.524, so I didn't make that connection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18783) Perforce plugin help file missing
SCM/JIRA link daemon commented on JENKINS-18783 Perforce plugin help file missing Code changed in jenkins User: Rob Petti Path: src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly http://jenkins-ci.org/commit/perforce-plugin/245af7fe5412f6c26cea80949b16a938c1fe2f6e Log: FIXED JENKINS-18783 fixing charset help link This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18783) Perforce plugin help file missing
SCM/JIRA link daemon resolved JENKINS-18783 as Fixed Perforce plugin help file missing Change By: SCM/JIRA link daemon (30/Jul/13 3:34 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] [plot] (JENKINS-18644) Loading Overlay
cupcicm commented on JENKINS-18644 Loading Overlay It does not seem to be fixed in 1.525. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18801) perforce sync not working in multi depot environment
Rob Petti closed JENKINS-18801 as Cannot Reproduce perforce sync not working in multi depot environment Change By: Rob Petti (30/Jul/13 3:31 PM) Status: Open Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
Russell B commented on JENKINS-18674 TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened Correct - although the fix is in the master branch, it has yet to be pulled for the release candidate. I stated 1.525 because I assumed that the fix would be pulled in by now, sorry for the confusion. I'm not sure how to go about encouraging the administrators to do this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
