[JIRA] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Steve Todorov edited a comment on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 After upgrading to the latest 1.598 we had the same StackOverflow exception as everybody. Downgrading Maven Project Plugin to version 2.7.1 solved the issue for us. 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Steve Todorov commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 After upgrading to the latest 1.598 we had the same StackOverflow exception as everybody. Downgrading Maven Project Plugin to version 2.7.1 solves 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
acdha commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 We had the same problem – a quick dpkg install of http://pkg.jenkins-ci.org/debian/binary/jenkins_1.597_all.deb fixed it 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Jesse Glick resolved JENKINS-26595 as Duplicate StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 Change By: Jesse Glick (27/Jan/15 9: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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
James Green commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 Tried two of our Maven builds and they both fail with StackOverflowError on deploying the first artefact to Nexus too. Downgraded to 1.597 fixed it here also. 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andrey Boytsov commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 @Robert Thanks for sharing. Actually, your issue looks like exactly JENKINS-26595 to me. Is there something I missed? They have very similar error logs and they both appear while "Deploying the main artifact". I added a new issue: JENKINS-26613. Not sure whether it is a duplicate of JENKINS-26601 or not. 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Robert Hook commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 My error is similar, but from a different stage: using settings config with name settings.xml using global settings config with name settings.xml Maven RedeployPublisher use remote maven settings from : /tmp/settings7301547955354275431.xml [INFO] Deployment in http://XXX:8081/artifactory/libs-snapshot-local (id=libs-snapshot,uniqueVersion=true) Deploying the main artifact X-1.13.0-SNAPSHOT.jar FATAL: null java.lang.StackOverflowError at java.lang.Exception.(Exception.java:102) at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy82.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy82.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy82.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy82.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy82.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor631.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) and so on without end 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andrey Boytsov commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 @Andreas Thanks! Might be. The log looks somewhat like JENKINS-26601, but not exactly: Building on master in workspace /var/lib/jenkins/jobs/<...> Fetching changes from the remote Git repository Fetching upstream changes from <...> Checking out Revision <...> Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.Exception.(Exception.java:102) at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy62.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy62.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy62.lookup(Unknown Source) (... and so on) 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andreas Horst commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 @Andrey Maybe you are experiencing JENKINS-26601 instead of this one. A couple of jobs could be "fixed" as described but I also ran into JENKINS-26601 which is independent from the post-build step. 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andrey Boytsov commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 Problem appeared after upgrading to 1.598 >> Removing the Deploy Maven Artifacts post-build steps fixes the builds. Did not work for me. Actually, we never had that post-build step. Are there any other known workarounds? Thanks in advance, Andrey. 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Robert Hook commented on JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 same here - downgraded to 1.597 resolved 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] [maven-plugin] (JENKINS-26595) StackOverflowError in Maven RedeployPublisher after upgrade to 1.598
Andreas Horst created JENKINS-26595 StackOverflowError in Maven RedeployPublisher after upgrade to 1.598 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 26/Jan/15 10:31 AM Description: After upgrading to 1.598 jobs with a Deploy Maven Artifacts post-build step fail with the following StackOverflowError: Maven RedeployPublisher use remote X maven settings from : /home/jenkins/.m2/settings.xml [INFO] Deployment in http://x.x.x/nexus/content/repositories/x-snapshots/ (id=x,uniqueVersion=true) Deploying the main artifact x-0.0.1-SNAPSHOT.jar FATAL: null java.lang.StackOverflowError at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) Removing the Deploy Maven Artifacts post-build steps fixes the builds. Other post-build steps (e.g. Sonar) work fine. Environment: Jenkins 1.598, Maven Integration Plugin 2.8 Project: Jenkins Labels: jenkins maven deploy Priority: Major Reporter: Andreas Horst 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.
