[JIRA] [core] (JENKINS-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Sounds reasonable enough, I'll keep an eye out when it happens again and try to increase the heap. Thanks! 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-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Yes, restarting Jenkins seems to be a good workaround. 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-23149) ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed
Mircea D commented on JENKINS-23149 ArtifactArchiver throws java.lang.OutOfMemoryError: Map failed Happened to me too on 1.604... I'm trying to see if restarting Jenkins works as a workaround. 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] [m2release-plugin] (JENKINS-15871) Maven Release Plugin doesn't properly escape user's passwords during release
Mircea D commented on JENKINS-15871 Maven Release Plugin doesn't properly escape user's passwords during release @Daniel, yes, true, I've only seen that after posting the comment. I apologize. 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] [m2release-plugin] (JENKINS-14781) Maven Release Plugin performs build without goals
Mircea D commented on JENKINS-14781 Maven Release Plugin performs build without goals It's the same thing for the ^ (batch escape character). 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] [m2release-plugin] (JENKINS-15871) Maven Release Plugin doesn't properly escape user's passwords during release
Mircea D edited a comment on JENKINS-15871 Maven Release Plugin doesn't properly escape user's passwords during release Could you please reopen this? A colleague of mine is using ^ in her password (which is the escape character for batch files) and that also doesn't seem to be escaped properly: [INFO] Executing: cmd.exe /X /C "svn --username xyz --password * --no-auth-cache --non-interactive commit --file C:\Windows\TEMP\maven-scm-1733557087.commit --targets C:\Windows\TEMP\maven-scm-998404332084042799-targets" [INFO] Working directory: C:\Program Files (x86)\Jenkins\workspace\Server trunk Notifying upstream projects of job completion Join notifier requires a CauseAction [INFO] [INFO] Reactor Summary: [INFO] [INFO] Server Product ... FAILURE [01:44 min] [INFO] Base Module . SKIPPED [INFO] Simulator ... SKIPPED [INFO] Module ... SKIPPED [INFO] Gate Module . SKIPPED [INFO] Host Module . SKIPPED [INFO] Server ... SKIPPED [INFO] DB Import SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:45 min [INFO] Finished at: 2015-02-27T16:54:50+01:00 [INFO] Final Memory: 11M/30M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project ***-server-product: Unable to commit files [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E170001: Commit failed (details follow): [ERROR] svn: E170001: Unable to connect to a repository at URL 'http://***:8080/svnlls/projects/***/server/trunk' [ERROR] svn: E170001: OPTIONS of 'http://***:8080/svnlls/projects/***/server/trunk': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (http://***:8080) [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project ***-server-product: Unable to commit files Provider message: The svn command failed. Command output: svn: E170001: Commit failed (details follow): svn: E170001: Unable to connect to a repository at URL 'http://***:8080/svnlls/projects/***/server/trunk' svn: E170001: OPTIONS of 'http://***:8080/svnlls/projects/***/server/trunk': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (http://***:8080) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
[JIRA] [m2release-plugin] (JENKINS-15871) Maven Release Plugin doesn't properly escape user's passwords during release
Mircea D commented on JENKINS-15871 Maven Release Plugin doesn't properly escape user's passwords during release Could you please reopen this? A colleague of mine is using ^ in her password and that also doesn't seem to be escaped properly: [INFO] Executing: cmd.exe /X /C "svn --username xyz --password * --no-auth-cache --non-interactive commit --file C:\Windows\TEMP\maven-scm-1733557087.commit --targets C:\Windows\TEMP\maven-scm-998404332084042799-targets" [INFO] Working directory: C:\Program Files (x86)\Jenkins\workspace\Server trunk Notifying upstream projects of job completion Join notifier requires a CauseAction [INFO] [INFO] Reactor Summary: [INFO] [INFO] Server Product ... FAILURE [01:44 min] [INFO] Base Module . SKIPPED [INFO] Simulator ... SKIPPED [INFO] Module ... SKIPPED [INFO] Gate Module . SKIPPED [INFO] Host Module . SKIPPED [INFO] Server ... SKIPPED [INFO] DB Import SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:45 min [INFO] Finished at: 2015-02-27T16:54:50+01:00 [INFO] Final Memory: 11M/30M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project ***-server-product: Unable to commit files [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E170001: Commit failed (details follow): [ERROR] svn: E170001: Unable to connect to a repository at URL 'http://***:8080/svnlls/projects/***/server/trunk' [ERROR] svn: E170001: OPTIONS of 'http://***:8080/svnlls/projects/***/server/trunk': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (http://***:8080) [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project ***-server-product: Unable to commit files Provider message: The svn command failed. Command output: svn: E170001: Commit failed (details follow): svn: E170001: Unable to connect to a repository at URL 'http://***:8080/svnlls/projects/***/server/trunk' svn: E170001: OPTIONS of 'http://***:8080/svnlls/projects/***/server/trunk': authorization failed: Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge (http://***:8080) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.
