[JIRA] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Bryan Kelly commented on JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin +1 I just ran into this situation as well. If other have a better work around I would be interested. Currently I think the only solution that works for us is to configure the settings.xml file for each slave which cause more maintenance overhead and loses the value provided by Jenkins performing the Maven Artifact Deployment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Bryan Kelly commented on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported I just completed upgrading to 1.564 and have captured the following logging information. It would appear that our environment is reporting these following stack traces repeatedly. I will continue to monitor the environment. We did upgrade the master node to java 8 as well as apart of this upgrade. May 25, 2014 11:00:07 AM SEVERE hudson.remoting.ExportTable unexportByOid Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 5 iota=171 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.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:352) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: Object was recently deallocated #5 (ref.0) : hudson.CloseProofOutputStream Created at Sun May 25 10:24:01 CDT 2014 at hudson.remoting.ExportTable$Entry.(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.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at hudson.util.StreamTaskListener.writeObject(StreamTaskListener.java:161) at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:888) at hudson.Launcher$ProcStarter.start(Launcher.java:355) at hudson.Launcher$ProcStarter.join(Launcher.java:362) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:77) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.plugins.git.GitTool.forNode(GitTool.java:79) at hudson.plugins.git.GitSCM.getGitExe(GitSCM.java:679) at hudson.plugins.git.GitSCM.getGitExe(GitSCM.j
[JIRA] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man edited a comment on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue most of these jobs were created on 1.518 version of jenkins if my memory serves me right. However, config_hidden.xml is similar to jobs that were created on the older version of jenkins prior to the 1.518 version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man edited a comment on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue. Most of those jobs were created on 1.518 version of jenkins if my memory serves me right. However, config_hidden is similar to jobs that were created on the older version of jenkins prior to the 1.518 upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-import] (JENKINS-18816) Jobs disappear when upgrading from Jenkins 1.514 to 1.523
xylo man commented on JENKINS-18816 Jobs disappear when upgrading from Jenkins 1.514 to 1.523 I attempted to upgrade an instance today as well and was met with the same issues. New jobs had a configuration similar to the visible attached to this issue. Most of those jobs were created on 1.514 version of jenkins if my memory serves me right. However, config_hidden is similar to jobs that were created on the older version of jenkins prior to the 1.514 upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
