org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed

Jenkins JIRA | Henrique Viecili | 5 years ago
  1. 0

    When performing a release the final 'git clone' and 'git push' executed do not take the username:password defined in the scm's connection/developerConnection. Scenario: - git repository wrapped by gitblit to provide user authorization/authentication, thus we need to specify a user/pass to be able to fetch/push. [pom.xml] {{ <scm> <connection>scm|git|http://ciuser:cipass@git.repo.url</connection> <developerConnection>scm|git|[fetch=]http://ciuser:cipass@git.repo.url[push=]http://ciuser:cipass@git.repo.url</developerConnection> </scm> }} jenkins job configutaion: {{ SCM Repository URL: http://ciuser:cipass@git.repo.url Checkout/merge to local branch: master Merge before build: checked }} log snippet: {{ [INFO] Release preparation complete. [INFO] [INFO] Checking out the project to perform the release ... [INFO] Executing: /bin/sh -c cd /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target && git clone http://developers.myreks.com/gitblit/git/development/reksplatform-event-bus-model.git /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target/checkout [INFO] Working directory: /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target [INFO] --- maven-release-plugin:2.0:perform (default-cli) @ reksplatform-event-bus-model --- [ERROR] The git-clone command failed. [JENKINS] Archiving /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/pom.xml to /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/modules/com.myreks.event$reksplatform-event-bus-model/builds/2012-02-10_20-02-18/archive/com.myreks.event/reksplatform-event-bus-model/1.1.8-SNAPSHOT/reksplatform-event-bus-model-1.1.8-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.683s [INFO] Finished at: Fri Feb 10 20:02:31 BRST 2012 [INFO] Final Memory: 6M/16M [INFO] ------------------------------------------------------------------------ mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed cause : Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) 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:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:122) at hudson.maven.Maven3Builder.call(Maven3Builder.java:74) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:139) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:171) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:343) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:289) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:269) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:131) ... 29 more channel stopped Finished: FAILURE }} I'm not sure if the bug is in m2release, scm-git or jenkins itself, so I decided to post it here since you should have a broader vision of all these tools.

    Jenkins JIRA | 5 years ago | Henrique Viecili
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed
  2. 0

    When performing a release the final 'git clone' and 'git push' executed do not take the username:password defined in the scm's connection/developerConnection. Scenario: - git repository wrapped by gitblit to provide user authorization/authentication, thus we need to specify a user/pass to be able to fetch/push. [pom.xml] {{ <scm> <connection>scm|git|http://ciuser:cipass@git.repo.url</connection> <developerConnection>scm|git|[fetch=]http://ciuser:cipass@git.repo.url[push=]http://ciuser:cipass@git.repo.url</developerConnection> </scm> }} jenkins job configutaion: {{ SCM Repository URL: http://ciuser:cipass@git.repo.url Checkout/merge to local branch: master Merge before build: checked }} log snippet: {{ [INFO] Release preparation complete. [INFO] [INFO] Checking out the project to perform the release ... [INFO] Executing: /bin/sh -c cd /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target && git clone http://developers.myreks.com/gitblit/git/development/reksplatform-event-bus-model.git /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target/checkout [INFO] Working directory: /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/target [INFO] --- maven-release-plugin:2.0:perform (default-cli) @ reksplatform-event-bus-model --- [ERROR] The git-clone command failed. [JENKINS] Archiving /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/workspace/pom.xml to /opt/apps/jenkins/jobs/reksplatform-event-bus-model-release/modules/com.myreks.event$reksplatform-event-bus-model/builds/2012-02-10_20-02-18/archive/com.myreks.event/reksplatform-event-bus-model/1.1.8-SNAPSHOT/reksplatform-event-bus-model-1.1.8-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.683s [INFO] Finished at: Fri Feb 10 20:02:31 BRST 2012 [INFO] Final Memory: 6M/16M [INFO] ------------------------------------------------------------------------ mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed cause : Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) 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:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:122) at hudson.maven.Maven3Builder.call(Maven3Builder.java:74) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:139) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:171) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:343) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:289) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:269) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:131) ... 29 more channel stopped Finished: FAILURE }} I'm not sure if the bug is in m2release, scm-git or jenkins itself, so I decided to post it here since you should have a broader vision of all these tools.

    Jenkins JIRA | 5 years ago | Henrique Viecili
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project reksplatform-event-bus-model: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed
  3. 0

    svn checkout failed during release:perform build

    Stack Overflow | 6 months ago | Sanu Mishra
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project IDLUtils: Unable to checkout from SCM Provider message: SVN checkout failed. Command output: svn: URL 'svn://scm.*/tags/IDLUtils-1.0' doesn't exist
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [jira] Created: (MRELEASE-702) Could not release project due to GIT clone error when working in sub-directory - Grokbase

    grokbase.com | 5 months ago
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:perform (default-cli) on project WelcomTutorial: Unable to checkout from SCM Provider message: The git-clone command failed. Command output: fatal: '/app/DINB/bamboo-agent-home/xml-data/build-dir/WTUT-RELEASE-JOB1/ParentPom' does not appear to be a git repository fatal: The remote end hung up unexpectedly
  6. 0

    I tried to build a maven project on a Windows Server 2008. I used the build goal of the maven project, but Subversion could not commit the changed poms. The workspace did not contain any locked files (svn status). The error does not occur when I build with the maven-release-plugin on jenkins. The error also occurs with the m2release plugin. The following error only occurs during a Windows build: 0:56:09 message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on project cosa-scm-k1-win175: Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09 10:56:09 cause : Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09 10:56:09 Stack trace : 10:56:09 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on project cosa-scm-k1-win175: Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09 10:56:09 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) 10:56:09 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 10:56:09 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 10:56:09 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) 10:56:09 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) 10:56:09 at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) 10:56:09 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) 10:56:09 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 10:56:09 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 10:56:09 at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 10:56:09 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 10:56:09 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 10:56:09 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 10:56:09 at java.lang.reflect.Method.invoke(Method.java:597) 10:56:09 at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) 10:56:09 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) 10:56:09 at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) 10:56:09 at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) 10:56:09 at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) 10:56:09 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 10:56:09 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 10:56:09 at hudson.remoting.Request$2.run(Request.java:326) 10:56:09 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 10:56:09 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 10:56:09 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 10:56:09 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 10:56:09 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 10:56:09 at java.lang.Thread.run(Thread.java:662) 10:56:09 Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09 10:56:09 at org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:242) 10:56:09 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) 10:56:09 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) 10:56:09 ... 27 more 10:56:09 Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09 10:56:09 at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:165) 10:56:09 at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:145) 10:56:09 at org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:76) 10:56:09 at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:78) 10:56:09 at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:507) 10:56:09 at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:474) 10:56:09 at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:459) 10:56:09 at org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:234) 10:56:09 ... 29 more 10:56:10 channel stopped 10:56:11 Email was triggered for: Failure 10:56:11 Sending email for trigger: Failure 10:56:12 Failed to send e-mail to hudsonrelease because no e-mail address is known, and no default e-mail domain is configured 10:56:12 An attempt to send an e-mail to empty list of recipients, ignored. 10:56:12 Finished: FAILURE

    Jenkins JIRA | 4 years ago | epikur2412
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on project cosa-scm-k1-win175: Unable to commit files 10:56:09 Provider message: 10:56:09 The svn command failed. 10:56:09 Command output: 10:56:09 svn: E155004: Commit failed (details follow): 10:56:09 svn: E155004: Working copy 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' locked. 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) 10:56:09 Type 'svn help' for usage. 10:56:09

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.apache.maven.shared.release.scm.ReleaseScmCommandException

      Unable to checkout from SCM Provider message: The git-clone command failed. Command output: error: The requested URL returned error: 401 while accessing http://git.repo.url/info/refs fatal: HTTP request failed

      at org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute()
    2. Maven Release Manager
      DefaultReleaseManager.perform
      1. org.apache.maven.shared.release.phase.CheckoutProjectFromScm.execute(CheckoutProjectFromScm.java:171)
      2. org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:343)
      3. org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:289)
      4. org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:269)
      4 frames
    3. org.apache.maven
      PerformReleaseMojo.execute
      1. org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:131)
      1 frame
    4. Maven Plugin
      DefaultBuildPluginManager.executeMojo
      1. org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
      1 frame
    5. Maven Core
      DefaultMaven.execute
      1. org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
      2. org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
      3. org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
      4. org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
      5. org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
      6. org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
      7. org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
      8. org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
      9. org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
      9 frames
    6. M3 Interceptor
      Maven3Launcher.main
      1. org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
      1 frame
    7. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      4. java.lang.reflect.Method.invoke(Method.java:597)
      4 frames
    8. Plexus
      Launcher.launch
      1. org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
      2. org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
      2 frames
    9. M3 Agent
      Maven3Main.launch
      1. org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
      1 frame
    10. Hudson Maven Embedder
      Maven3Builder.call
      1. hudson.maven.Maven3Builder.call(Maven3Builder.java:122)
      2. hudson.maven.Maven3Builder.call(Maven3Builder.java:74)
      2 frames
    11. Hudson :: Remoting Layer
      Request$2.run
      1. hudson.remoting.UserRequest.perform(UserRequest.java:118)
      2. hudson.remoting.UserRequest.perform(UserRequest.java:48)
      3. hudson.remoting.Request$2.run(Request.java:287)
      3 frames
    12. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      2. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      3. java.util.concurrent.FutureTask.run(FutureTask.java:138)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      5. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      6. java.lang.Thread.run(Thread.java:662)
      6 frames