[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
Dmitry Korotkov resolved JENKINS-22497 as Duplicate Variables inside FILE content are not replaced Duplicate to JENKINS-21333 Change By: Dmitry Korotkov (29/May/14 6:03 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Momin Noor Khan created JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin Issue Type: Improvement Assignee: ragesh_nair Components: rebuild Created: 29/May/14 6:04 AM Description: Rebuild plugin crashes if a parameterized job contains JIRA Issues parameter (probably it would crash for JIRA Version parameter as well). If possible the plugin should be modified to handle custom parameter types in some way. Project: Jenkins Priority: Major Reporter: Momin Noor Khan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
Dmitry Korotkov reopened JENKINS-22497 Variables inside FILE content are not replaced I misread description. Reopening the request. Change By: Dmitry Korotkov (29/May/14 6:11 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/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-21333) Variable injected with EnvInject not supported
Dmitry Korotkov
commented on JENKINS-21333
Variable injected with EnvInject not supported
The proposed change will not help. For the specified example:
${FILE:${ENV:INSTALL_DIR}/Success.html}
Captured group will be ${ENV:INSTALL_DIR which will not be parsed by replaceVars as you expect.
I see the support for nested expressions as a bad idea - it would be even possible to run into endless recursion if it is not done right.
What do you think if we allow constructs like:
${FILE:ENV:SOMEVAR}
which will be resolved into file content of the specified file?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-21333) Variable injected with EnvInject not supported
Oleg Nenashev commented on JENKINS-21333 Variable injected with EnvInject not supported @Dmitry I think you should consider the usage of Token Macro 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/d/optout.
[JIRA] [rebuild] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Oleg Nenashev commented on JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin Please provide logs/stacktraces for the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Oleg Nenashev updated JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin Change By: Oleg Nenashev (29/May/14 8:13 AM) Component/s: jira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-23230) SauceOnDemandReportPublisher processBuildOutput - wrong build number, not getting job-name
Michał Matyjek
created JENKINS-23230
SauceOnDemandReportPublisher processBuildOutput - wrong build number, not getting job-name
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
sauce-ondemand
Created:
29/May/14 8:23 AM
Description:
I am not getting job-name updated on SauceLabs. Also the build name is off.
My job logs have something like this:
2014-05-29 01:00:35 INFO MyTest:10 - SauceOnDemandSessionID=2...4 job-name=com.test.MyTest
But in plugin's log I see:
May 29, 2014 12:59:24 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction hasSauceOnDemandResults
Inside hasSauceOnDemandResults v1.64
May 29, 2014 12:59:24 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction hasSauceOnDemandResults
Checking to see if project has Sauce results
May 29, 2014 12:59:24 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction hasSauceOnDemandResults
Found Sauce results
May 29, 2014 12:59:27 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction hasSauceOnDemandResults
Inside hasSauceOnDemandResults v1.64
May 29, 2014 12:59:27 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction hasSauceOnDemandResults
Checking to see if project has Sauce results
May 29, 2014 12:59:27 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandProjectAction getSauceBuildActions
No Sauce Build Action found for myJenkinsJob #595 adding a new one
May 29, 2014 12:59:28 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper setUp
Setting up Sauce Build Wrapper
May 29, 2014 12:59:28 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1 buildEnvVars
Creating Sauce environment variables
May 29, 2014 1:00:39 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper processBuildOutput
Adding build action to myJenkinsJob #595
May 29, 2014 1:00:39 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher processBuildOutput
Adding build action to myJenkinsJob/com.company:git-repo #595
May 29, 2014 1:00:39 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandBuildAction retrieveJobIdsFromSauce
Performing Sauce REST retrieve results for myJenkinsJob__595
May 29, 2014 1:00:41 AM INFO hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher processBuildOutput
Notice how the build name differs in SauceOnDemandReportPublisher (wrong one - with "/com.company:git-repo" appended) vs SauceOnDemandBuildWrapper (correct one).
And finally, when the plugin performs the REST update - not only does it set the build number to a wrong name, but also does not set the job name.
Here's the sample JSON body for an update:
{"passed":true,"build":"myJenkinsJob_com_company_git_repo__595","public":true}
This used to work for me back in 1.74 I think. I do not remember any changes in between that could have broken this on our end.
Environment:
Jenkins ver. 1.565 / plugin version 1.87
Project:
Jenkins
Priority:
Major
Reporter:
Michał Matyjek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Ramakrishna Bejawar commented on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. The Plugin Seems to be older version 1.1.2, May be I'll check by upgrading to latest. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Momin Noor Khan updated JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin Error encountered on trying to rebuild a job which contains jira issues parameter. Change By: Momin Noor Khan (29/May/14 10:06 AM) Attachment: rebuild-error.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/d/optout.
[JIRA] [jira] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Momin Noor Khan commented on JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin @Oleg Please find attached the screenshot, which shows the relevant stacktrace thrown by stapler. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
SCM/JIRA link daemon commented on JENKINS-23168 Allow to specify a Location where to deploy the slaves in the jclouds-plugin Code changed in jenkins User: Ignasi Barrera Path: jclouds-plugin/README.md jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/help-locationId.html jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java http://jenkins-ci.org/commit/jclouds-plugin/6468f207899048918af84135e49bba5eff3980d6 Log: JENKINS-23168: Allow to specify the Location where to deploy the slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
SCM/JIRA link daemon commented on JENKINS-23168 Allow to specify a Location where to deploy the slaves in the jclouds-plugin Code changed in jenkins User: Marat Mavlyutov Path: jclouds-plugin/README.md jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/help-locationId.html jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java http://jenkins-ci.org/commit/jclouds-plugin/1d01a17f69238dc58b59097c1d8cb35bede60c2a Log: Merge pull request #68 from nacx/location JENKINS-23168: Allow to specify the Location where to deploy the slaves Compare: https://github.com/jenkinsci/jclouds-plugin/compare/219dafe041b8...1d01a17f6923 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22977) Add results paging to the Jenkins API
Daniel Beck commented on JENKINS-22977 Add results paging to the Jenkins API semantically it doesn't make sense that you must switch from "builds" to "allBuilds" just to retrieve a larger result set. Returning all builds used to be essentially free. As of 1.485, it's insanely expensive. What would be a better solution, breaking backwards compatibility? There's a lot of things weird in Jenkins, but caused by the desire to remain backward compatible. Pagination API already exists, it's called XPath. https://builds.apache.org/job/PDFBox-ant/api/xml?tree=allBuildsnumberxpath=//allBuildposition%28%29%3C=10wrapper=builds https://builds.apache.org/job/PDFBox-ant/api/xml?tree=allBuildsnumberxpath=//allBuildposition%28%29%3E10%20and%20position%28%29%3C=20wrapper=builds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-23168) Allow to specify a Location where to deploy the slaves in the jclouds-plugin
Ignasi Barrera resolved JENKINS-23168 as Fixed Allow to specify a Location where to deploy the slaves in the jclouds-plugin Change By: Ignasi Barrera (29/May/14 10:29 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23229) Rebuild plugin is not compatible with JIRA plugin
Oleg Nenashev commented on JENKINS-23229 Rebuild plugin is not compatible with JIRA plugin Actually, newest versions of Rebuild Plugin provide an extension point for the Rebuild entry. JIRA Plugin should implement this extension point. I'll modify the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23229) [JIRA plugin] - Add support of rebuild actions (Rebuild Plugin)
Oleg Nenashev updated JENKINS-23229 [JIRA plugin] - Add support of rebuild actions (Rebuild Plugin) Change By: Oleg Nenashev (29/May/14 10:33 AM) Summary: Rebuildpluginisnotcompatiblewith [ JIRAplugin ]-Addsupportofrebuildactions(RebuildPlugin) Issue Type: Improvement NewFeature Assignee: ragesh_nair Component/s: rebuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4819) Enable/disable build step by one click
Oleg Nenashev updated JENKINS-4819 Enable/disable build step by one click Change By: Oleg Nenashev (29/May/14 10:36 AM) Component/s: core Component/s: www This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4819) Enable/disable build step by one click
Oleg Nenashev commented on JENKINS-4819 Enable/disable build step by one click A new extension point in the Core is required for the case. UI implementation should be done by plugins. I also think that the "Disabled" flag/enum could be useful for all extension points and descriptors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prereq-buildstep] (JENKINS-9467) jenkins-plugin-info macro assumes subversion when it can't find github
Oleg Nenashev updated JENKINS-9467 jenkins-plugin-info macro assumes subversion when it cant find github Fixed the component Change By: Oleg Nenashev (29/May/14 10:40 AM) Component/s: prereq-buildstep Component/s: www This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7244) [PATCH] Make link targets bigger
Oleg Nenashev updated JENKINS-7244 [PATCH] Make link targets bigger I'm not sure the patch stills actual Change By: Oleg Nenashev (29/May/14 10:42 AM) Component/s: core Component/s: www This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23120) FATAL: hudson.remoting.RequestAbortedException on Windows Slaves
Kay Abendroth commented on JENKINS-23120 FATAL: hudson.remoting.RequestAbortedException on Windows Slaves Git this today right in the middle of a running Job (Jenkins version 1.563). FATAL: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy67.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23120) FATAL: hudson.remoting.RequestAbortedException on Windows Slaves
Kay Abendroth edited a comment on JENKINS-23120 FATAL: hudson.remoting.RequestAbortedException on Windows Slaves Got this today right in the middle of a running Job (Jenkins version 1.563). FATAL: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy67.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.nio.channels.AsynchronousCloseException at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-23231) Add timeout config for SSH plugins
Amo Chumber created JENKINS-23231 Add timeout config for SSH plugins Issue Type: New Feature Assignee: Unassigned Components: ssh Created: 29/May/14 10:54 AM Description: Hello, While using the SSH plugin I continually get socket timeout errors. After some research (i'm not a java dev) I think the problem could be mitigated somewhat if I was able to configure the timeout value from within Jenkins. From my limited understanding Jenkins is calling the Jsch library which does have a variable for sockettimeout: http://epaul.github.io/jsch-documentation/javadoc/com/jcraft/jsch/Session.html#setTimeout(int) So similar to how we pass the host details and the keepalive settings can we add a field to configure the timeout? Apologies if this is not the place for this. Project: Jenkins Priority: Minor Reporter: Amo Chumber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Ashok Manji commented on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) @sstack - did you file a separate bug on this? I am also seeing this with v1.554.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Ashok Manji edited a comment on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) @sstack - did you file a separate bug on this? I am also seeing this with v1.554.1 and the issue was not present when we were on v1.534 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Ashok Manji created JENKINS-23232 SEVERE: I/O error in channel Chunked connection Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: error.log Components: cli, slave-setup Created: 29/May/14 11:57 AM Description: We use the jenkins-cli.jar to attach new slaves and this has been working successfully in v1.534, however when upgrading to v1.554.1, we are unable to do so and a "SEVERE: I/O error in channel Chunked connection" error occurs. Tested on linux slaves using java version "1.6.0_35" and "1.7.0_45" and the same error occurs. Attached console output to error.log Environment: Jenkins v1.554.1 running on CentOS 6.3 Project: Jenkins Labels: cli jenkins exception 1.554.1 severe Priority: Blocker Reporter: Ashok Manji This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [libvirt-slave] (JENKINS-23233) Libvirt does not shut down slaves after last upgrade of plugin
Hendrik Meiring created JENKINS-23233 Libvirt does not shut down slaves after last upgrade of plugin Issue Type: Bug Assignee: Philipp Bartsch Components: libvirt-slave Created: 29/May/14 12:07 PM Description: I am currently using the latest version of jenkins - 1.564. After upgrading the libvirt plugin from 1.8.0 to the latest 0.8.4 The slaves do not shut down again when idle. Downgrading the plugin fixes this. Project: Jenkins Priority: Major Reporter: Hendrik Meiring This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-23231) Add timeout config for SSH plugins
Oleg Nenashev commented on JENKINS-23231 Add timeout config for SSH plugins There're plenty of various timeouts in Jenkins (like hardcoded 4-min timeout in PingThreads). What result are you going to achieve by increasing the particular timeout? (just to elaborate the impact) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [global-build-stats] (JENKINS-23225) RFE - Add support for viewing statistics per folder
Frédéric Camblor commented on JENKINS-23225 RFE - Add support for viewing statistics per folder Agree This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
Liam McGregor commented on JENKINS-13357 Autoinstall JDK from download.oracle.com no longer works Do you have an example of how the manually downloaded java files names and directories must be? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
George Li commented on JENKINS-22830 Slow login w/ Active directory plugin I would second bumping up the priority as I am experiencing the same errors mentioned above. I am using the same workaround by downgrading to 1.36. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-18518) Red highlights not showing when clicking on indications
Steven Kuhlmann commented on JENKINS-18518 Red highlights not showing when clicking on indications Not sure if this is the same problem. Since upgrading to 1.6.0 (also tried 1.7.0 and 1.8.0) from 1.5.1 the indication links no longer go to the location of the error in the console. I have noticed that the link address no longer contains the problem identification key. For example, with 1.5.1 it displays as "http://xxx.xx.xxx.xx:8080/view/Gerrit-Master/job/MC-L64-Master2/14/consoleFull#-1905833836a24c50ac-0e61-402b-ae1d-a9d9d630b676" and since 1.6.0 it displays as "http://xxx.xx.xxx.xx:8080/view/Gerrit-Master/job/MC-L64-Master2/14/consoleFull". The problems are highlighted red but it always goes to the top of the console output. Jenkins Core: 1.532.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-18518) Red highlights not showing when clicking on indications
Steven Kuhlmann edited a comment on JENKINS-18518 Red highlights not showing when clicking on indications Not sure if this is the same problem. Since upgrading to 1.6.0 (also tried 1.7.0 and 1.8.0) from 1.5.1 the indication links no longer go to the location of the error in the console. I have noticed that the link address no longer contains the problem identification key. For example, with 1.5.1 it displays as "http://xxx.xx.xxx.xx:8080/view/Gerrit-Master/job/MC-L64-Master2/14/consoleFull#-1905833836a24c50ac-0e61-402b-ae1d-a9d9d630b676" and since 1.6.0 it displays as "http://xxx.xx.xxx.xx:8080/view/Gerrit-Master/job/MC-L64-Master2/14/consoleFull". The problems are highlighted red but it always goes to the top of the console output. Jenkins Core: 1.532.1 Linux Debian Server This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-18170) Remove issues on Github or stop using Jenkins Jira
dserodio commented on JENKINS-18170 Remove issues on Github or stop using Jenkins Jira It seems there are no more issues on Github This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
James Coleman commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly There seems to be a similar problem with cvs plugin upon cvs update. A recursive directory causes job to hang forever. Using strace can see process is recursing into directory to multiple levels . . . CVS Plugin 2.11 http://wiki.jenkins-ci.org/display/JENKINS/CVS+Plugin Jenkins ver. 1.562 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-23234) cvs update hang when recursive symlink in directory
James Coleman created JENKINS-23234 cvs update hang when recursive symlink in directory Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 29/May/14 3:16 PM Description: Jenkins job hangs forever doing cvs update. A recursive directory causes job to hang forever. Using strace can see process is recursing into directory to multiple levels . . . A previous build job created symlinks to . in some directories in checkout area. CVS Plugin 2.11 http://wiki.jenkins-ci.org/display/JENKINS/CVS+Plugin Jenkins ver. 1.562 This problem with git plugin seems to have been a similar problem: https://issues.jenkins-ci.org/browse/JENKINS-17186 Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly Environment: redhat fc19 jenkins 1.562 cvs_plugin 2.11 cvs ssh Project: Jenkins Priority: Major Reporter: James Coleman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23221) Security Matrix too has has form too large
Paul Roth resolved JENKINS-23221 as Fixed Security Matrix too has has form too large Thanks, it looks like the rolestrategy plugin sounds like the way we'll move forward. Change By: Paul Roth (29/May/14 3:19 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/d/optout.
[JIRA] [slave-utilization] (JENKINS-23132) 4-5min delay at end of job on slave
banoss commented on JENKINS-23132 4-5min delay at end of job on slave This can often be seen when running plugins such as build failure analyser or disk usage that scan things periodically or at the end of each build. You might get a clue from the main jenkins log or monitor thread usage during this time - try jvmtop. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22915) In HockeyApp plugin it seems like the Clean up old versions at HockeyApp is no longer working
Ken Yee commented on JENKINS-22915 In HockeyApp plugin it seems like the Clean up old versions at HockeyApp is no longer working FYI, if you uncheck the "use new api", it apparently won't delete previous versions if you tell it to only keep N versions. It'll just silently fail to upload. I had to tell Jenkins to use the 1.0.5 version of the HockeyApp 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/d/optout.
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Joe Littlejohn created JENKINS-23235 buildWithParameters does not return queue location Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/May/14 4:44 PM Description: When creating builds using /build, the result is a 201 response where the Location header points to the queue item that represents the new build. Example: curl -X POST -v "http://jenkins.mycompany.com/job/test-job/build" * Adding handle: conn: 0xf28b90 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0xf28b90) send_pipe: 1, recv_pipe: 0 * About to connect() to jenkins.mycompany.com port 80 (#0) * Trying 10.10.10.10... * Connected to jenkins.mycompany.com (10.10.10.10) port 80 (#0) POST /job/test-job/build HTTP/1.1 User-Agent: curl/7.32.0 Host: jenkins.mycompany.com Accept: */* HTTP/1.1 201 Created Date: Thu, 29 May 2014 16:38:29 GMT * Server Jetty(8.y.z-SNAPSHOT) is not blacklisted Server: Jetty(8.y.z-SNAPSHOT) Location: http://jenkins.mycompany.com/queue/item/3901/ Content-Length: 0 Connection: close Content-Type: text/plain; charset=UTF-8 * Closing connection 0 For parameterized builds we must use /buildWithParameters instead, however the response from /buildWithParameters does not contain the queue location: $ curl -X POST -v "http://jenkins.mycompany.com/job/parameterized-test-job/buildWithParameters" * Adding handle: conn: 0xa63c30 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0xa63c30) send_pipe: 1, recv_pipe: 0 * About to connect() to jenkins.mycompany.com port 80 (#0) * Trying 10.10.10.10... * Connected to jenkins.mycompany.com (10.10.10.10) port 80 (#0) POST /job/parameterized-test-job/buildWithParameters HTTP/1.1 User-Agent: curl/7.32.0 Host: jenkins.mycompany.com Accept: */* HTTP/1.1 302 Found Date: Thu, 29 May 2014 16:41:09 GMT * Server Jetty(8.y.z-SNAPSHOT) is not blacklisted Server: Jetty(8.y.z-SNAPSHOT) Location: http://jenkins.mycompany.com/job/parameterized-test-job/ Content-Length: 0 Connection: close Content-Type: text/plain; charset=UTF-8 * Closing connection 0 Environment: CentOS 6.4 Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Project: Jenkins Labels: rest api Priority: Major Reporter: Joe Littlejohn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Jason Miller edited a comment on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported We're seeing this error as well after upgrading from 1.551 (Java 6) to 1.565 (Java 7), though I haven't run into any issues so far aside from a lot of log spam: SEVERE: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 123 iota=252 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:300) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object was recently deallocated #123 (ref.0) : hudson.CloseProofOutputStream Created at Tue May 27 11:15:27 MDT 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82) at sun.reflect.GeneratedMethodAccessor467.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) at hudson.util.StreamTaskListener.writeObject(StreamTaskListener.java:161) at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.FilePath.act(FilePath.java:909) at hudson.FilePath.act(FilePath.java:893) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:566) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:522) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357) at hudson.scm.SCM.poll(SCM.java:374) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1449) at hudson.model.AbstractProject._poll(AbstractProject.java:1420) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:466) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:495) at
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Joe Littlejohn
updated JENKINS-23235
buildWithParameters does not return queue location
Change By:
Joe Littlejohn
(29/May/14 4:47 PM)
Description:
Whencreatingbuildsusing/build,theresultisa201responsewheretheLocationheaderpointstothequeueitemthatrepresentsthenewbuild.Example:{code}curl-XPOST-vhttp://jenkins.mycompany.com/job/test-job/build*Addinghandle:conn:0xf28b90*Addinghandle:send:0*Addinghandle:recv:0*Curl_addHandleToPipeline:length:1*-Conn0(0xf28b90)send_pipe:1,recv_pipe:0*Abouttoconnect()tojenkins.mycompany.comport80(#0)*Trying10.10.10.10...*Connectedtojenkins.mycompany.com(10.10.10.10)port80(#0)POST/job/test-job/buildHTTP/1.1User-Agent:curl/7.32.0Host:jenkins.mycompany.comAccept:*/*HTTP/1.1201CreatedDate:Thu,29May201416:38:29GMT*ServerJetty(8.y.z-SNAPSHOT)isnotblacklistedServer:Jetty(8.y.z-SNAPSHOT)Location:http://jenkins.mycompany.com/queue/item/3901/Content-Length:0Connection:closeContent-Type:text/plain;charset=UTF-8*Closingconnection0{code}Forparameterizedbuildswemustuse/buildWithParametersinstead,howevertheresponsefrom/buildWithParametersdoesnotcontainthequeuelocation:{code}$curl-XPOST-vhttp://jenkins.mycompany.com/job/parameterized-test-job/buildWithParameters*Addinghandle:conn:0xa63c30*Addinghandle:send:0*Addinghandle:recv:0*Curl_addHandleToPipeline:length:1*-Conn0(0xa63c30)send_pipe:1,recv_pipe:0*Abouttoconnect()tojenkins.mycompany.comport80(#0)*Trying10.10.10.10...*Connectedtojenkins.mycompany.com(10.10.10.10)port80(#0)POST/job/parameterized-test-job/buildWithParametersHTTP/1.1User-Agent:curl/7.32.0Host:jenkins.mycompany.comAccept:*/*HTTP/1.1302FoundDate:Thu,29May201416:41:09GMT*ServerJetty(8.y.z-SNAPSHOT)isnotblacklistedServer:Jetty(8.y.z-SNAPSHOT)Location:http://jenkins.mycompany.com/job/parameterized-test-job/Content-Length:0Connection:closeContent-Type:text/plain;charset=UTF-8*Closingconnection0{code}
Theexpectedresponsetothisrequestisa201withtheLocationheadercontainingtheURLofaqueueitem(exactlywhat/builddoes).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher] (JENKINS-15301) HTML Publisher failure: Failed to extract directory from slave
mcrooney commented on JENKINS-15301 HTML Publisher failure: Failed to extract directory from slave Unfortunately, while I wrote this plugin, I'm not familiar with remote slaves or what is causing this. If anyone is able to take a look it at and submit a pull request at https://github.com/jenkinsci/htmlpublisher-plugin, it would be greatly appreciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prqa] (JENKINS-23166) PRQA - duplicated message from headers files (case 11364)
Mads Nielsen updated JENKINS-23166 PRQA - duplicated message from headers files (case 11364) Change By: Mads Nielsen (29/May/14 5:25 PM) Summary: PRQA-duplicatedmessagefromheadersfiles (case11364) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prqa] (JENKINS-23166) PRQA - duplicated message from headers files (case 11364)
Mads Nielsen commented on JENKINS-23166 PRQA - duplicated message from headers files (case 11364) Hi Michal I am not to sure what is causing this, this is more likely a configuration issue, and something you have to switch off/on when running the analysis command. Have you tried contacting PRQA about it, maybe if you enabled the logging plugin as described on the wiki, and sending us the log output will allow us to shed new light on your issue. Best regards, Mads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-18560) Extra when forming cmd line arguments for parameters containing a space
Michael Fowler resolved JENKINS-18560 as Duplicate Extra when forming cmd line arguments for parameters containing a space Change By: Michael Fowler (29/May/14 6:23 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Daniel Beck commented on JENKINS-23235 buildWithParameters does not return queue location Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23236) PatchSetCreatedEvent now has a kind field
Joshua Kugler created JENKINS-23236 PatchSetCreatedEvent now has a kind field Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 29/May/14 6:40 PM Description: https://gerrit-review.googlesource.com/#/c/57231/ merged in a change to PatchSetCreatedEvent that adds a kind field and ChangeKind enum. This allows Gerrit to communicate the kind of change, and the listener to take certain actions based on this change kind. Example if change kind is "NO_CODE_CHANGE" (i.e. just a commit message change) then the listener could decide not to trigger a build. At this point, this is just a heads up, as this is in master, and not released but since it was "our" bug report that precipitated this change, we'd very much like to see this in Gerrit Trigger soon. Project: Jenkins Labels: plugin git gerrit gerrit-trigger Priority: Major Reporter: Joshua Kugler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22841) javax.servlet.ServletException at slave SystemInfo
Lance Zimmerman commented on JENKINS-22841 javax.servlet.ServletException at slave SystemInfo Looks like I hit it with Ubuntu 14.04 64-bit, Jenkins 1.565, Java 1.7.0_55 Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.jar!/hudson/slaves/SlaveComputer/systemInfo.jelly:41:61: st:include java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.commons.jelly.JellyTagException:
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Joe Littlejohn commented on JENKINS-23235 buildWithParameters does not return queue location Ah sorry, the 'Affected Version/s' field wouldn't accept the version and I forgot to add it to the description. It's Jenkins 1.559. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Joe Littlejohn updated JENKINS-23235 buildWithParameters does not return queue location Change By: Joe Littlejohn (29/May/14 6:58 PM) Environment: Jenkins1.559 CentOS6.4Java(TM)SERuntimeEnvironment(build1.7.0_25-b15) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23235) buildWithParameters does not return queue location
Daniel Beck resolved JENKINS-23235 as Duplicate buildWithParameters does not return queue location Between Jenkins and almost a thousand plugins, Jira simply cannot handle the possible versions. Issue duplicates JENKINS-13546 which was fixed in 1.561. Change By: Daniel Beck (29/May/14 7:01 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4207) LC_ALL=cs_CZ.ISO8859-2 on solaris 9
Daniel Beck resolved JENKINS-4207 as Not A Defect LC_ALL=cs_CZ.ISO8859-2 on solaris 9 As indicated in the comments and the linked Groovy issue, this is an issue with JDK on Solaris, not Jenkins. Change By: Daniel Beck (29/May/14 7:04 PM) Status: InProgress Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23237) EC2 Plugin continuously spins up instances when a job is stuck in queue.
Kevin R. created JENKINS-23237 EC2 Plugin continuously spins up instances when a job is stuck in queue. Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 29/May/14 7:10 PM Description: I just recently came across an old job of mine. It is not specified to run on any label, but ALL of my instances are reserved to run jobs that are explicitly tied to them. So when this job was accidentally started, it got stuck in the queue. The EC2 plugin then proceeded to continuously spin up instances of the first AMI that I have in my configuration. It's unacceptably bad Environment: CentOS6.4 Jenkins 1.565-1.1 EC2 Plugin 1.21 Matrix Build Plugin 1.2 Project: Jenkins Priority: Major Reporter: Kevin R. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux Is this a bug in Jenkins or in the xvfb 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/d/optout.
[JIRA] [ec2] (JENKINS-23237) EC2 Plugin continuously spins up instances when a job is stuck in queue.
Kevin R. updated JENKINS-23237 EC2 Plugin continuously spins up instances when a job is stuck in queue. Change By: Kevin R. (29/May/14 7:14 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
Richard Reynolds created JENKINS-23238 Single and Multi select multi level choice does not work. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: extended-choice-parameter Created: 29/May/14 7:40 PM Description: Multi level select functionality doesn't appear to work at all. There are various issues when creating the configuration e.g. not ticking the default parameter checkbox results in exceptions on save. Also gives warning about not selecting property key which isn't relevant for this type. More importantly however when you do manage to get it to save the config the dropdowns don't appear on the build page, only the param name and description do with blank space between them. Environment: Windows 7,linux (RHEL 6.4) Chrome, IE and Mozilla. Current stable Jenkins build. Project: Jenkins Labels: parameter plugin Priority: Major Reporter: Richard Reynolds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9564) Nested Repeatable dropbox change values when used back/forward buttons in Chrome
Daniel Beck resolved JENKINS-9564 as Duplicate Nested Repeatable dropbox change values when used back/forward buttons in Chrome Duplicates JENKINS-18435 (that issue has more watchers and indicates it's still a problem). Change By: Daniel Beck (29/May/14 8:18 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4311) Hudson fails build upon failure to delete a target folder
Daniel Beck resolved JENKINS-4311 as Not A Defect Hudson fails build upon failure to delete a target folder This looks like it happens in the user's build script rather than Jenkins code. Also, needs to show that no other process (search indexer, virus scanner, ...) access the files that fail to delete to show this is a Jenkins issue. Also, needs to be reproduced on recent version of Jenkins. Change By: Daniel Beck (29/May/14 8:24 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-8723) Computing changelog fails: incomplete argument list
Daniel Beck updated JENKINS-8723 Computing changelog fails: incomplete argument list Does this issue still occur in recent Jenkins/CVS Plugin versions? Change By: Daniel Beck (29/May/14 8:27 PM) Priority: Critical Major Component/s: cvs Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23237) EC2 Plugin continuously spins up instances when a job is stuck in queue.
Kevin R. commented on JENKINS-23237 EC2 Plugin continuously spins up instances when a job is stuck in queue. Actually, this seems to happen for any job in the queue, even if it's waiting for a different kind of slave to spin up... Again, on Jenkins v1.565-1.1 This did not happen when I was on v1.560 before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23237) EC2 Plugin continuously spins up instances when a job is stuck in queue.
Kevin R. commented on JENKINS-23237 EC2 Plugin continuously spins up instances when a job is stuck in queue. Seems like this PR would solve this issue: https://github.com/jenkinsci/ec2-plugin/pull/86 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources] (JENKINS-23239) Test failures running mvn install on source
Douglas Rosser created JENKINS-23239 Test failures running mvn install on source Issue Type: Bug Assignee: Unassigned Components: lockable-resources Created: 29/May/14 9:04 PM Description: Running: lockable-resources-plugin (master)$ mvn install ... Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 INFO INFO BUILD FAILURE INFO INFO Total time: 8.191 s INFO Finished at: 2014-05-29T14:02:45-08:00 INFO Final Memory: 19M/187M INFO ERROR Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (default-test) on project lockable-resources: There are test failures. ERROR ERROR Please refer to /Users/drosser/workstuff/lockable-resources-plugin/target/surefire-reports for the individual test results. ERROR - Help 1 ERROR ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. ERROR Re-run Maven using the -X switch to enable full debug logging. ERROR ERROR For more information about the errors and possible solutions, please read the following articles: ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException From /Users/drosser/workstuff/lockable-resources-plugin/target/surefire-reports/InjectedTest.txt --- Test set: InjectedTest --- Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 4.651 sec FAILURE! org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite(org.jvnet.hudson.test.junit.FailedTest) Time elapsed: 0.007 sec ERROR! java.lang.ArrayIndexOutOfBoundsException: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77) at java.util.HashMap.putMapEntries(HashMap.java:511) at java.util.HashMap.putAll(HashMap.java:784) at com.thoughtworks.xstream.core.util.OrderRetainingMap.init(OrderRetainingMap.java:36) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldsFor(FieldDictionary.java:76) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:127) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:143) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:102) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:898) at com.thoughtworks.xstream.XStream.marshal(XStream.java:887) at com.thoughtworks.xstream.XStream.toXML(XStream.java:860) at hudson.XmlFile.write(XmlFile.java:183) at jenkins.model.Jenkins.save(Jenkins.java:2642) at jenkins.model.Jenkins.setNoUsageStatistics(Jenkins.java:979) at org.jvnet.hudson.test.HudsonTestCase.setUp(HudsonTestCase.java:326) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.setUp(JellyTestSuiteBuilder.java:133) at org.jvnet.hudson.test.junit.GroupedTest.run(GroupedTest.java:46) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at
[JIRA] [hipchat] (JENKINS-23240) hipchat link in hipchat client is broken.
Alex Gray created JENKINS-23240 hipchat link in hipchat client is broken. Issue Type: Bug Assignee: Unassigned Components: hipchat Created: 29/May/14 9:21 PM Description: We are using hipchat version: 0.1.5-SNAPSHOT When we get a notification via hipchat, the link that we receive points to something like: file:///Applications/HipChat.app/Contents/Resources/nulljob/build-dialer/603/ That link is obviously broken. I thought it would be a link to Jenkins or something. Any ideas how this can fixed/tweaked? My config.xml looks like: jenkins.plugins.hipchat.HipChatNotifier_-HipChatJobProperty plugin="hipchat@0.1.5-SNAPSHOT" room123456789/room startNotificationtrue/startNotification notifySuccesstrue/notifySuccess notifyAbortedtrue/notifyAborted notifyNotBuilttrue/notifyNotBuilt notifyUnstabletrue/notifyUnstable notifyFailuretrue/notifyFailure notifyBackToNormaltrue/notifyBackToNormal /jenkins.plugins.hipchat.HipChatNotifier_-HipChatJobProperty jenkins.plugins.hipchat.HipChatNotifier plugin="hipchat@0.1.5-SNAPSHOT" authTokenMY_AUTH_KEY/authToken room123456789/room /jenkins.plugins.hipchat.HipChatNotifier Project: Jenkins Priority: Major Reporter: Alex Gray This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources] (JENKINS-23239) Test failures running mvn install on source
Douglas Rosser commented on JENKINS-23239 Test failures running mvn install on source Okay, this may be Not A Bug. Running "mvn install" with $JAVA_HOME pointing at an older version of Java results in zero errors. [lockable-resources-plugin (master)]$ mvn --version Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T09:37:52-08:00) Maven home: /usr/local/Cellar/maven/3.2.1/libexec Java version: 1.6.0_65, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.9.3", arch: "x86_64", family: "mac" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19151) stop build running very slowly
x jenkins commented on JENKINS-19151 stop build running very slowly I am currently using version 1 and the problem disappeared. After executing the body of work just published the results of the test using the plugin xunit and cppcheck results. This only happened when the job failed or stopped using the link STOP in the executions's queue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [global-build-stats] (JENKINS-23225) RFE - Add support for viewing statistics per folder
Steven Christou commented on JENKINS-23225 RFE - Add support for viewing statistics per folder It looks like there were some code changes: https://github.com/jenkinsci/global-build-stats-plugin/commit/60d83f56620a0b372d12f664970ef84ea18668ab to provide better support for folders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accelerated-build-now] (JENKINS-23241) exception on nodes jenkins
x jenkins created JENKINS-23241 exception on nodes jenkins Issue Type: Improvement Assignee: Unassigned Components: accelerated-build-now Created: 29/May/14 9:54 PM Description: I run multiconfiguration job on four nodes (2 opensuse, 2 ubuntu). Each node has 1GB of RAM. The build run a script that compile, packing and run the test the code c++. In many cases the test and compilation is heavy and delayed. On several occasions in the console output showing the work abort with this message "Java.io.IOException: error = 12, Can not allocate memory" Environment: ubuntu precise 12.04 1GB RAM JAVA_ARGS=-Xmx900m -XX:MaxPermSize=700m (/etc/default/jenkins) Project: Jenkins Labels: java exception heap Priority: Major Reporter: x jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task] (JENKINS-22248) Support multiple launches per workspace
SCM/JIRA link daemon commented on JENKINS-22248 Support multiple launches per workspace Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java src/main/java/org/jenkinsci/plugins/durabletask/WindowsBatchScript.java http://jenkins-ci.org/commit/durable-task-plugin/6655d258234e49c5be38bd80ab5fb6817584e995 Log: FIXED JENKINS-22248 Using unique ID for each run to allow multiple executions to run on 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/d/optout.
[JIRA] [durable-task] (JENKINS-22248) Support multiple launches per workspace
SCM/JIRA link daemon resolved JENKINS-22248 as Fixed Support multiple launches per workspace Change By: SCM/JIRA link daemon (29/May/14 9:59 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/d/optout.
[JIRA] [job-node-stalker] (JENKINS-23242) Node Stalker breaks if stalked job is renamed
dserodio created JENKINS-23242 Node Stalker breaks if stalked job is renamed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: job-node-stalker Created: 29/May/14 10:39 PM Description: If I rename a job that another job is "stalking", the link between the jobs is broken. When I go to edit the following job, I see the following error: No such project ‘followed-job’. Did you mean ‘followed-job-renamed’? If I try to run the following job, I get this error: NODE STALKER The job followed-job does not exist! Please check your configuration! Environment: Jenkins 1.554 Project: Jenkins Priority: Major Reporter: dserodio This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23243) Add url redirect support for renamed projects
Mason Blaylock moved JENKINS-23243 Add url redirect support for renamed projects Change By: Mason Blaylock (29/May/14 10:51 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 81 23243 Workflow: jira JNJira Component/s: core Component/s: www This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
abayer created JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master Issue Type: Bug Assignee: Unassigned Components: core Created: 30/May/14 12:11 AM Description: So I went to try to see the usage for a slave on builds.apache.org, and the page had no builds on it. I eventually noticed the "Calculation in progress" bit and thought "Oh, ok, I'll leave this up and check again later". That was a mistake. Now there are 30+ threads on the master like the ones in https://gist.github.com/abayer/88e390e3f0859f8b64e2 - i.e., a whole ton of HTTP POST requests to /computer/foo/timeline/data, all but one blocking on the one that's running, and the one that's running takes a long time to finish. This means (a) that the build history page for a slave is useless and (b) that we're churning CPU/IO and, I'm guessing, doing so repeatedly without caching, since when I check it now, even an hour and a half later, there's no data on the page. Environment: 1.554.1 with JENKINS-22822 backported onto it Project: Jenkins Priority: Critical Reporter: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-23217) Prefix/Suffix Start Slave Command does not automatically append/prepend
Daniel Beck commented on JENKINS-23217 Prefix/Suffix Start Slave Command does not automatically append/prepend There are shells that do not support (notably fish). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21398) Skip build if Verified label is automatically copied to patch set
rin_ne resolved JENKINS-21398 as Duplicate Skip build if Verified label is automatically copied to patch set Actual fix with patch was opened as new issue. So close this. Change By: rin_ne (30/May/14 2:56 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Lawrence Ong commented on JENKINS-22830 Slow login w/ Active directory plugin This bug basically killed our LDAP server by making a really bad query. I would bump this as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Lawrence Ong updated JENKINS-22830 Slow login w/ Active directory plugin Change By: Lawrence Ong (30/May/14 5:57 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
