Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17796

Maven 2/3 _-Project Job Unable to commit files svn: E155004

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • maven-plugin
    • Jenkins V.1513 / Windows Server 2008 / Subversion 1.7.8 / Tortoise svn client 1.7.8 / Maven 3.x

      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-17796] Maven 2/3 _-Project Job Unable to commit files svn: E155004

          Michael Kopf added a comment -

          I had a similar problem on a multi module project and got it fixed. It is described in JENKINS-19547. Maybe it helps.

          Michael Kopf added a comment - I had a similar problem on a multi module project and got it fixed. It is described in JENKINS-19547 . Maybe it helps.

          epikur2412 added a comment -

          Thank you for the advice. But my job does not build , the error appears furthermore.

          epikur2412 added a comment - Thank you for the advice. But my job does not build , the error appears furthermore.

          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)

          Not jenkins issue, because maven-release-plugin calls svn client that doesn't belong to jenkins plugins.
          http://stackoverflow.com/questions/16433933/svn-e155004-path-of-resouce-is-already-locked

          Kanstantsin Shautsou added a comment - 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) Not jenkins issue, because maven-release-plugin calls svn client that doesn't belong to jenkins plugins. http://stackoverflow.com/questions/16433933/svn-e155004-path-of-resouce-is-already-locked

          Daniel Beck added a comment -

          integer Depends on how the workspace got broken. May well have been Jenkins or one of its plugins.

          Daniel Beck added a comment - integer Depends on how the workspace got broken. May well have been Jenkins or one of its plugins.

          epikur2412 added a comment -

          a direct call "mvn -B -Dresume=false release:prepare release:perform" as "Execute windows batch command" does not lock any space.

          epikur2412 added a comment - a direct call "mvn -B -Dresume=false release:prepare release:perform" as "Execute windows batch command" does not lock any space.

            Unassigned Unassigned
            epikur2412 epikur2412
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: