[JIRA] [cvs] (JENKINS-18329) ConcurrentModificationException during pooling in version 2.9
Michael Clarke commented on JENKINS-18329 ConcurrentModificationException during pooling in version 2.9 To give us a fighting change of resolving this, could you provide us with the stacktrace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
kutzi assigned JENKINS-18262 to Jesse Glick HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work Change By: kutzi (16/Jun/13 8:46 AM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18366) Jetty should be used rather than Winstone for embedded deployments
Michael D created JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Jun/13 9:06 AM Description: Hudson recently switched to using Jetty as an embedded servlet engine. It has a very small size, and very very good performance. Put bluntly, the current use of Winstone SUCKS, and due to its threaded design will cause performance to slow to a crawl at 240+ requests a minute even on high end hardware with aggressive varnish caching. At the same time using an external Java EE container isn't that easy, so by following hudson and switching to Jetty we get the best of both worlds. Thanks md_5 Project: Jenkins Priority: Major Reporter: Michael D This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam commented on JENKINS-18262 HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work I worked with this issue in JENKINS-18259, and sent a pull request with https://github.com/jenkinsci/jenkins/pull/814 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-15688) Add list-jobs comand to CLI
Oliver Gondža resolved JENKINS-15688 as Fixed Add list-jobs comand to CLI Command available since jenkins-1.494 Change By: Oliver Gondža (16/Jun/13 9:38 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
Oliver Gondža created JENKINS-18367 list-jobs command returns 0 even though view or item group does not exist Issue Type: Bug Assignee: Oliver Gondža Components: cli Created: 16/Jun/13 9:42 AM Project: Jenkins Priority: Minor Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
Oliver Gondža commented on JENKINS-18367 list-jobs command returns 0 even though view or item group does not exist Proposed fix: https://github.com/jenkinsci/jenkins/pull/815 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
SCM/JIRA link daemon resolved JENKINS-18367 as Fixed list-jobs command returns 0 even though view or item group does not exist Change By: SCM/JIRA link daemon (16/Jun/13 11:01 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
SCM/JIRA link daemon commented on JENKINS-18367 list-jobs command returns 0 even though view or item group does not exist Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/cli/ListJobsCommand.java core/src/test/java/hudson/cli/ListJobsCommandTest.java http://jenkins-ci.org/commit/jenkins/1ef9cae2dea05eb358c3abab59ac4fa60f5fd257 Log: FIXED JENKINS-18367 Use non-zero return code in case list-jobs CLI command fails This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
SCM/JIRA link daemon commented on JENKINS-18367 list-jobs command returns 0 even though view or item group does not exist Code changed in jenkins User: Christoph Kutzinski Path: core/src/main/java/hudson/cli/ListJobsCommand.java core/src/test/java/hudson/cli/ListJobsCommandTest.java http://jenkins-ci.org/commit/jenkins/1e7b82aea0720bef0f2223b71582518932da6b16 Log: Merge pull request #815 from olivergondza/list_jobs_retval FIXED JENKINS-18367 Use non-zero return code when list-jobs CLI fails Compare: https://github.com/jenkinsci/jenkins/compare/5bc00fffcc0a...1e7b82aea072 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Frédéric Camblor commented on JENKINS-17248 java.lang.NullPointerException by start I tried to migrate my local workspace from 1.424 to 1.508 and I encountered the problem, full stacktrace : Jun 16, 2013 1:35:42 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /Users/fcamblor/Documents/projects/Jenkins-Plugins/global-build-stats/./work/global-build-stats.xml hudson.util.IOException2: Unable to read /Users/fcamblor/Documents/projects/Jenkins-Plugins/global-build-stats/./work/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.Plugin.load(Plugin.java:239) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.init(Jenkins.java:849) 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: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.lang.NullPointerException cause-message : null class : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path: /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number : 2 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 com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at hudson.XmlFile.unmarshal(XmlFile.java:166) ... 9 more Caused by: java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:472) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) ... 18 more Jun 16, 2013 1:35:43 PM hudson.WebAppMain$2 run Problem is I cannot reproduce it now (problem fired only once, and after a jenkins restart it didn't pop anymore). If someone have any more input to reproduce the problem (backuped global-build-stats.xml for instance), it would be helpful for a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18367) list-jobs command returns 0 even though view or item group does not exist
dogfood commented on JENKINS-18367 list-jobs command returns 0 even though view or item group does not exist Integrated in jenkins_main_trunk #2621 FIXED JENKINS-18367 Use non-zero return code in case list-jobs CLI command fails (Revision 1ef9cae2dea05eb358c3abab59ac4fa60f5fd257) Result = SUCCESS ogondza : 1ef9cae2dea05eb358c3abab59ac4fa60f5fd257 Files : core/src/test/java/hudson/cli/ListJobsCommandTest.java core/src/main/java/hudson/cli/ListJobsCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cron_column] (JENKINS-18313) H cron syntax - cannot specify between 10 pm and 6 am
Daniel Beck commented on JENKINS-18313 H cron syntax - cannot specify between 10 pm and 6 am It's documented here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.html Excerpt: The codeH/code symbol can be used with a range. For example, codeH H(0-7) * * */code means some time between 12:00 AM (midnight) to 7:59 AM. You can also use step intervals with codeH/code, with or without ranges. Have you tried "0-6", maybe it fails because your example crosses into the next day? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18313) H cron syntax - cannot specify between 10 pm and 6 am
Daniel Beck updated JENKINS-18313 H cron syntax - cannot specify between 10 pm and 6 am Change By: Daniel Beck (16/Jun/13 1:47 PM) Component/s: core Component/s: cron_column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18313) H cron syntax - cannot specify between 10 pm and 6 am
Daniel Beck edited a comment on JENKINS-18313 H cron syntax - cannot specify between 10 pm and 6 am The syntax since 1.510 is documented here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.html Excerpt: The codeH/code symbol can be used with a range. For example, codeH H(0-7) * * */code means some time between 12:00 AM (midnight) to 7:59 AM. You can also use step intervals with codeH/code, with or without ranges. Have you tried "0-6", maybe it fails because your example crosses into the next day? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Julien Carsique updated JENKINS-17248 java.lang.NullPointerException by start Attached a backup of global-build-stats.xml but I didn't test if it reproduces the issue. Change By: Julien Carsique (16/Jun/13 2:24 PM) Attachment: global-build-stats.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-12911) Clearecase Plugin Not Detecting Changes
Timothy Lantz commented on JENKINS-12911 Clearecase Plugin Not Detecting Changes I was poking around a bit further. It looks like using the same version of the plugin, but changing Jenkins versions reproduces the problem. If I run on 1.424, the plugin correctly gets the path separators by checking RemoteLaucher.isUnix() (which returns true). However, now on Jenkins 1.518, it is producing a Windows separator matching _expression_ by using isUnix on the hudson.Launcher that gets passed in, which is returning false. Haven't had a chance to dig deeper, but will try later tonight or tomorrow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-12911) Clearecase Plugin Not Detecting Changes
Timothy Lantz commented on JENKINS-12911 Clearecase Plugin Not Detecting Changes Poking more - I think this may be specific to when the RemoteLauncher is decorated by an environment. The anonymous inner class for this case in Launcher.java doesn't override isUnix. So what happens is that the path check ends up being run instead (from the basic Launcher), and the isUnix variable that is normally taken from the SlaveComputer gets ignored. Seems like a simple change, but not sure what else it may break. I will give it a try. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Frédéric Camblor commented on JENKINS-17248 java.lang.NullPointerException by start Doesn't reproduce the issue 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-18368) Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Timothy Lantz created JENKINS-18368 Decorated Launcher Does Not Maintain isUnix for RemoteLauncher Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 17/Jun/13 3:31 AM Description: RemoteLauncher's isUnix attribute is supplied on construction for slaves. However, when the RemoteLauncher is passed through decorateByEnv, because the anonymous class created in this method does not override isUnix, it delegates back to the base Launcher's File.pathSeparatorChar==':' check. The value for the slave passed into RemoteLauncher on construction is lost. A similar problem occurs with decorateByPrefix. This will cause a problem if any downstream logic depends on the Launcher's isUnix value for a process launched on a slave with a different isUnix value than the master. For example, with a Windows master and a Linux slave, the wrong file path separator is selected in a regex on the history output, and so the SCM polling does not accurately pick up changes. Environment: Reproducible with Windows master, Linux slaves Project: Jenkins Priority: Major Reporter: Timothy Lantz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
